Back to CVE records
Medium 5.8Published May 7, 2026

CVE-2026-42279solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID

Updated under an hour ago ()

Does this affect you?

It affects solidtime-io solidtime and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
5.8 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
Weakness (CWE)
CWE-639
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
May 8, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
solidtime-io solidtime
solidtime_io:solidtime (from the name)
= 0.12.0
CNA record
solidtime solidtime
solidtime:solidtime
0.12.0
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.