User compromise via authenticated dangerous-file upload
Published Jan 4, 2025 · Updated Feb 11, 2025
Unrestricted file upload in Optimizely EPiServer.CMS.UI before 12.32.0 allows remote authenticated users to upload dangerous files. Optimizely has not identified the responsible upload handler; its advisory states that file-type validation accepts active formats such as .docm and .html. An application user must later access the stored file, at which point its active content can execute malicious actions in that user's context and compromise the user's system.
Summary
What happened
Unrestricted file upload in Optimizely EPiServer.CMS.UI before 12.32.0 allows remote authenticated users to upload dangerous files. Optimizely has not identified the responsible upload handler; its advisory states that file-type validation accepts active formats such as .docm and .html. An application user must later access the stored file, at which point its active content can execute malicious actions in that user's context and compromise the user's system.
The record
- CVE
- CVE-2025-22389
- Published
- Jan 4, 2025
- Updated
- Feb 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1204.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 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
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