solidtime 0.12.0
Approved changes feed: RSS · Atom
cpe:2.3:a:solidtime:solidtime:0.12.0:*:*:*:*:*:*:*part: a version: 0.12.0 update: *
| Vendor | Solidtime (bb1ec63c-e37d-5b31-be16-86cce5e89314) |
|---|---|
| Product | Solidtime (fce02d97-a1e6-5d16-aeab-3fdb572ff822) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/solidtime-io/solidtime |
purl2cpe | 2026-07-28 16:41:04.142331 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42279 |
vulnerable | 2026-06-08 08:03:16.113986 |
solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID
MEDIUM (5.8)
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.
Published: 2026-05-08T03:57:31.727Z
Updated: 2026-05-08T10:38:51.086Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.