Stored script execution via unencoded site description
Published Feb 2, 2024 · Updated May 9, 2025
Stored cross-site scripting in MRCMS 3.0 allows remote attackers to execute JavaScript in browsers through crafted site metadata. The saveinfo action stores an HTML event handler from config.description, while the public About page renders the stored value without output encoding. Authenticated administrative access and an About-page visit are required; execution can expose or alter data available to the affected browser.
Summary
What happened
Stored cross-site scripting in MRCMS 3.0 allows remote attackers to execute JavaScript in browsers through crafted site metadata. The saveinfo action stores an HTML event handler from config.description, while the public About page renders the stored value without output encoding. Authenticated administrative access and an About-page visit are required; execution can expose or alter data available to the affected browser.
The record
- CVE
- CVE-2024-24160
- Published
- Feb 2, 2024
- Updated
- May 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 2, 2024CVE publishedPublication date reported by the CVE source.
- May 9, 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.
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
- MRCMS 3.0 stored-XSS 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