Authenticated file overwrite via event_id traversal
Published Jul 30, 2025 · Updated Jul 30, 2025
Path traversal in affected Bugsink releases allows remote authenticated users with a valid DSN to overwrite files via crafted event_id input. The get_filename_for_event_id function joined event_id directly to INGEST_STORE_BASE_DIR without validating or normalizing it as a UUID. Writes are limited to paths accessible to the Bugsink process and remain within the container filesystem in containerized deployments.
Summary
What happened
Path traversal in affected Bugsink releases allows remote authenticated users with a valid DSN to overwrite files via crafted event_id input. The get_filename_for_event_id function joined event_id directly to INGEST_STORE_BASE_DIR without validating or normalizing it as a UUID. Writes are limited to paths accessible to the Bugsink process and remain within the container filesystem in containerized deployments.
The record
- CVE
- CVE-2025-54433
- Published
- Jul 30, 2025
- Updated
- Jul 30, 2025
- Vendor
- Bugsink
- Product
- Bugsink
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2025CVE publishedPublication date reported by the CVE source.
- Jul 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.3
- Affected versionversion=>= 1.5.0, < 1.5.5
- Affected versionversion=>= 1.6.0, < 1.6.4
- Affected versionversion=>= 1.7.0, < 1.7.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo