# CVE-2026-33345: solidtime vulnerable to IDOR in private projects

> Authenticated employees can access private project details they are not authorized to view due to missing authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-354j-rx28-jjxm

## What is CVE-2026-33345?

CVE-2026-33345 is a medium-severity missing authorization vulnerability in solidtime-io solidtime, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

solidtime is an open-source time-tracking app. Prior to version 0.11.6, the project detail endpoint GET /api/v1/organizations/{org}/projects/{project} allows any authenticated Employee to access any project in the organization by UUID, including private projects they are not a member of. The index() endpoint correctly applies the visibleByEmployee() scope, but show() does not. This issue has been patched in version 0.11.6.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-33345?

It affects 1 product.


Products: Solidtime Solidtime.

## How do I fix CVE-2026-33345?

No fix has been published for CVE-2026-33345 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33345 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33345 exists.

## Other vulnerabilities in solidtime-io solidtime

- [CVE-2026-42279](https://insights.sbomify.com/CVE-2026-42279/): solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33345 and fix it if it is affected.

What it is: CVE-2026-33345 is a medium-severity missing authorization vulnerability in solidtime-io solidtime, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33345 exists.

Affected product: solidtime-io solidtime. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33345/ (Markdown: https://insights.sbomify.com/CVE-2026-33345/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33345
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33345
- OSV: https://osv.dev/vulnerability/CVE-2026-33345

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33345/
Summaries are generated and may contain mistakes; the official description above is the record.