Stored script execution via unencoded profile surname
Published Aug 1, 2025 · Updated Aug 1, 2025
Stored XSS in Microweber CMS 2.0.0 through 2.0.19 allows remote authenticated users to execute script in homepage visitors' browsers. The profile editor stores an unsanitized last-name value, and the homepage renders that value without output encoding. An attacker must log in and update a profile; the script runs when another user loads the homepage and can read that browser's session data or act within its session.
Summary
What happened
Stored XSS in Microweber CMS 2.0.0 through 2.0.19 allows remote authenticated users to execute script in homepage visitors' browsers. The profile editor stores an unsanitized last-name value, and the homepage renders that value without output encoding. An attacker must log in and update a profile; the script runs when another user loads the homepage and can read that browser's session data or act within its session.
The record
- CVE
- CVE-2025-51504
- Published
- Aug 1, 2025
- Updated
- Aug 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 1, 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
- Authenticated profile last-name stored-XSS 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