Stored script execution via unencoded username
Published May 5, 2025 · Updated May 6, 2025
Stored XSS in MRCMS 3.1.3 allows remote authenticated users to execute script in another user's browser through the edit page. The /admin/user/edit.do handler stores the attacker-controlled Username value without adequate filtering or HTML entity encoding before it is rendered. Administrative access is required to submit the value, and another user must view the stored content for the script to run in that user's browser context.
Summary
What happened
Stored XSS in MRCMS 3.1.3 allows remote authenticated users to execute script in another user's browser through the edit page. The /admin/user/edit.do handler stores the attacker-controlled Username value without adequate filtering or HTML entity encoding before it is rendered. Administrative access is required to submit the value, and another user must view the stored content for the script to run in that user's browser context.
The record
- CVE
- CVE-2025-4292
- Published
- May 5, 2025
- Updated
- May 6, 2025
- Vendor
- Marker
- Product
- MRCMS
- Classifications
- CWE-79, CWE-94, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 5, 2025CVE publishedPublication date reported by the CVE source.
- May 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=3.1.3
What conditions does exploitation require?
What is affected?
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.1.3 stored-XSS proof of vulnerabilityproof 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