Arbitrary file write via upload path traversal
Published Aug 21, 2025 · Updated Aug 21, 2025
Unrestricted file upload in Moss before 0.15 allows remote attackers to write files to arbitrary server paths through upload configuration. The uploadFunc flow leaves Path and Name unchanged for unmatched cases, then ActiveDriver supplies a traversal path that store.Set concatenates with res.FullPath without extension validation. CISA rates privileges required as none, although the published request contains a token header; successful use permits attacker-chosen files outside the upload directory.
Summary
What happened
Unrestricted file upload in Moss before 0.15 allows remote attackers to write files to arbitrary server paths through upload configuration. The uploadFunc flow leaves Path and Name unchanged for unmatched cases, then ActiveDriver supplies a traversal path that store.Set concatenates with res.FullPath without extension validation. CISA rates privileges required as none, although the published request contains a token header; successful use permits attacker-chosen files outside the upload directory.
The record
- CVE
- CVE-2025-55383
- Published
- Aug 21, 2025
- Updated
- Aug 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2025CVE publishedPublication date reported by the CVE source.
- Aug 21, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- GitHub issue #16 HTTP proof of conceptproof of concept · demonstrated
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