Path traversal in Solidtime Toggl importer creates directories
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
Solidtime, an open-source time-tracking app, is affected before 0.16.0. The Toggl ZIP importer uses project id values from uploaded projects.json files in file paths without validation, so path traversal sequences can escape the temporary directory and create directories at arbitrary writable host paths (CWE-22). Any registered user who can create an organization and use the import endpoint can reach the flaw. Distinguishable responses for existing and missing host files also reveal whether those files exist, causing minor availability impact and host layout disclosure.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
Solidtime is an open-source time-tracking app. Prior to 0.16.0, TogglDataImporter::importData() read attacker-controlled project id values from projects.json in uploaded ZIP imports and concatenated them into filesystem paths without validation. Because Spatie\TemporaryDirectory\TemporaryDirectory::path() creates missing parent directories, traversal sequences could escape the temporary sandbox and create directories at arbitrary writable host paths. Distinguishable ImportController responses for existing versus missing targets exposed whether suffix-constrained host paths derived from projects_users/{id}.json or tasks/{id}.json existed, because the importer always appended .json. Any registered user able to create an organization and use POST /api/v1/organizations/{org}/import with type=toggl_data_importer could reach the flaw, potentially causing minor availability impact through directory exhaustion and disclosing host layout information. This issue is fixed in version 0.16.0.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| solidtime-io | solidtime | before 0.16.0 | 0.16.0 | Patch available | CNA |
- solidtime Vendorsolidtime-io Affected before 0.16.0 Fixed in 0.16.0 Patch available CNA
Remediation
Update solidtime to version 0.16.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA solidtime (solidtime-io) Fixed in 0.16.0
Vendor assessments
Timeline
- 2026-11-04 Threatist record created from CVE-2026-76806
- 2026-11-06 Priority changed: MEDIUM → LOW
- 2026-11-06 Affected versions changed · Red Hat
- 2026-11-06 CVSS score added · Red Hat
References
More solidtime-io vulnerabilities
- TI-2026-34821 Incorrect authorization in solidtime-io solidtime CVSS 3.1MEDIUM 4.3
Sources
- CVE-2026-76806 · CVE Program
- CVE-2026-76806 · NVD
- FIRST EPSS
- CVE-2026-76806 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences