CVE-2026-42279
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…
Does this matter?
Lower severity and a low EPSS score (0.27%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.8 MEDIUMCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
- EPSS
- 0.27% probability · 19th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-639
- Affected
- solidtime/solidtime
- Source
- security-advisories@github.com
References
- https://github.com/solidtime-io/solidtime/commit/b73aa543fdf5b61c37447307ab7277451296832cPatch
- https://github.com/solidtime-io/solidtime/releases/tag/v0.12.1Product, Release Notes
- https://github.com/solidtime-io/solidtime/security/advisories/GHSA-pmf9-pxq9-ccwrExploit, Vendor Advisory
- https://github.com/solidtime-io/solidtime/security/advisories/GHSA-pmf9-pxq9-ccwrExploit, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.