Reflected XSS via unsanitized pagename
Published Apr 7, 2021 · Updated Aug 4, 2024
Cross-site scripting in wcms 0.3.2 allows remote attackers to inject arbitrary web script and HTML via the pagename parameter. The Pagename class copies POST pagename data into session and global state, and wex/html.php echoes that value into a path attribute without output encoding. Exploitation requires a victim browser to process a crafted request; resulting script execution can compromise that browser session.
Summary
What happened
Cross-site scripting in wcms 0.3.2 allows remote attackers to inject arbitrary web script and HTML via the pagename parameter. The Pagename class copies POST pagename data into session and global state, and wex/html.php echoes that value into a path attribute without output encoding. Exploitation requires a victim browser to process a crafted request; resulting script execution can compromise that browser session.
The record
- CVE
- CVE-2020-24138
- Published
- Apr 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
- Reflected XSS proof-of-concept payloadproof of concept · unverified
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