CVE-2026-42279 solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID
An attacker with update permissions can modify time entries belonging to other organizations by supplying a known UUID, leading to unauthorized data modification.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-42279?
CVE-2026-42279 is a medium-severity missing authorization vulnerability in solidtime-io solidtime, published on 8 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official 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.
Weakness: CWE-639
Which versions are affected by CVE-2026-42279?
It affects 1 product.
Products include Solidtime Solidtime.
How do I fix CVE-2026-42279?
No fix has been published for CVE-2026-42279 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-42279 being exploited?
There is no known exploitation of CVE-2026-42279 in the wild and no public exploit code.
Other vulnerabilities in solidtime-io solidtime
Sources
Also known as GHSA-pmf9-pxq9-ccwr.