Stored script execution via disabled MIME allowlist
Published Mar 5, 2025 · Updated Mar 6, 2025
Arbitrary file upload in REDAXO CMS before 5.18.3 allows remote authenticated users to store active content through MediaPool. The MediaPool upload path accepts a crafted .1html filename because the allowed_mime_types list is disabled by default, so extension filtering does not reject its HTML content. A backend account with MediaPool access can publish the file; another user's visit executes embedded JavaScript and can deliver malicious content.
Summary
What happened
Arbitrary file upload in REDAXO CMS before 5.18.3 allows remote authenticated users to store active content through MediaPool. The MediaPool upload path accepts a crafted .1html filename because the allowed_mime_types list is disabled by default, so extension filtering does not reject its HTML content. A backend account with MediaPool access can publish the file; another user's visit executes embedded JavaScript and can deliver malicious content.
The record
- CVE
- CVE-2025-27411
- Published
- Mar 5, 2025
- Updated
- Mar 6, 2025
- Vendor
- REDAXO
- Product
- REDAXO CMS
- Classifications
- CWE-434, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Mar 6, 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=< 5.18.3
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
- GitHub advisory MediaPool upload 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