solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| solidtime-io | solidtime | = 0.12.0 | — | No fix listed | CNA |
- solidtime Vendorsolidtime-io Affected = 0.12.0 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-42279
References
More solidtime-io vulnerabilities
- TI-2026-34821 Incorrect authorization in solidtime-io solidtime CVSS 3.1MEDIUM 4.3
- TI-2026-85134 Path traversal in Solidtime Toggl importer creates directories CVSS 3.1MEDIUM 6.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences