Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33345: CWE-639: Authorization Bypass Through User-Controlled Key in solidtime-io solidtime

0
Medium
VulnerabilityCVE-2026-33345cvecve-2026-33345cwe-639
Published: Tue Mar 24 2026 (03/24/2026, 19:30:27 UTC)
Source: CVE Database V5
Vendor/Project: solidtime-io
Product: solidtime

Description

CVE-2026-33345 is an authorization bypass vulnerability in the open-source time-tracking app solidtime prior to version 0. 11. 6. The flaw exists in the project detail endpoint GET /api/v1/organizations/{org}/projects/{project}, which allows any authenticated employee to access project details by UUID, including private projects they are not authorized to view. While the index() endpoint correctly restricts project visibility, the show() endpoint does not enforce membership checks, leading to unauthorized data exposure. This vulnerability has a CVSS score of 6. 5 (medium severity) and does not require user interaction but does require authenticated access. No known exploits are currently reported in the wild. The issue was patched in version 0. 11.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/24/2026, 20:02:02 UTC

Technical Analysis

CVE-2026-33345 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the solidtime open-source time-tracking application. The vulnerability arises because the show() endpoint (GET /api/v1/organizations/{org}/projects/{project}) fails to apply proper access control checks on project visibility. Specifically, any authenticated employee within an organization can retrieve details of any project by specifying its UUID, regardless of whether they are a member of that project or if the project is private. This contrasts with the index() endpoint, which correctly applies the visibleByEmployee() scope to restrict project listings to those the employee is authorized to see. The lack of proper authorization checks in the show() endpoint leads to unauthorized disclosure of project details, potentially exposing sensitive business information. The vulnerability affects all versions prior to 0.11.6, where the issue has been patched. Exploitation requires authentication but no additional user interaction, and the attack vector is network-based with low complexity. The CVSS v3.1 score is 6.5, reflecting high confidentiality impact but no impact on integrity or availability. No known exploits have been reported in the wild as of the publication date.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive project information within an organization. Attackers who are authenticated employees can access private project details they are not authorized to view, potentially exposing confidential business data, project plans, timelines, or proprietary information. This can lead to insider threats, data leakage, and loss of competitive advantage. Although the vulnerability does not allow modification or deletion of data, the confidentiality breach alone can have significant reputational and operational consequences. Organizations using solidtime for time tracking and project management, especially those handling sensitive or regulated data, face increased risk of internal data exposure. The impact is magnified in larger organizations with multiple projects and strict compartmentalization of information. Since exploitation requires valid employee credentials, the threat is primarily from malicious insiders or compromised accounts.

Mitigation Recommendations

To mitigate this vulnerability, organizations should upgrade solidtime to version 0.11.6 or later, where the authorization bypass has been fixed. Until the upgrade is applied, administrators should consider restricting access to the affected endpoints through network segmentation or API gateway policies that enforce strict access controls. Implementing additional application-layer authorization checks or custom middleware to verify project membership before returning project details can serve as a temporary workaround. Monitoring and auditing API access logs for unusual access patterns to project details by employees not assigned to those projects can help detect exploitation attempts. Enforcing strong authentication mechanisms and minimizing the number of employees with access to sensitive projects reduces risk. Finally, educating employees about the importance of credential security and monitoring for compromised accounts will help prevent abuse of this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-18T22:15:11.813Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c2ea08f4197a8e3b6b6437

Added to database: 3/24/2026, 7:46:16 PM

Last enriched: 3/24/2026, 8:02:02 PM

Last updated: 3/24/2026, 8:52:52 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses