No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 08 May 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 08 May 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Solidtime-io
Solidtime-io solidtime |
|
| Vendors & Products |
Solidtime-io
Solidtime-io solidtime |
Fri, 08 May 2026 05:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | solidtime is an open-source time-tracking app. In version 0.12.0, the PUT /api/v1/organizations/{organization}/time-entries/{timeEntry} API accepts a route-bound timeEntry from another organization when the caller has time-entries:update:all in the URL organization, allowing a known foreign time-entry UUID to be modified and rebound to objects in the caller's organization. This issue has been patched in version 0.12.1. | |
| Title | solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-08T10:38:51.086Z
Reserved: 2026-04-26T11:53:27.716Z
Link: CVE-2026-42279
Updated: 2026-05-08T10:38:33.282Z
Status : Received
Published: 2026-05-08T05:16:11.063
Modified: 2026-05-08T11:16:28.670
Link: CVE-2026-42279
No data.
OpenCVE Enrichment
Updated: 2026-05-08T07:30:02Z