Stored XSS via unsanitized nickname rendering
Published Jul 26, 2021 · Updated Aug 4, 2024
Stored XSS in RPCMS 1.8 and earlier allows remote authenticated users to execute script in readers' browsers through a crafted nickname. The updatePsw function stores the nickname POST value without sanitization, and Author::index inserts it into page metadata and the assigned title. A user account is required to plant the payload, and another user must view an article by that account for the script to run in that reader's RPCMS origin.
Summary
What happened
Stored XSS in RPCMS 1.8 and earlier allows remote authenticated users to execute script in readers' browsers through a crafted nickname. The updatePsw function stores the nickname POST value without sanitization, and Author::index inserts it into page metadata and the assigned title. A user account is required to plant the payload, and another user must view an article by that account for the script to run in that reader's RPCMS origin.
The record
- CVE
- CVE-2021-37393
- Published
- Jul 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 26, 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
- RPCMS CVE Submissionproof 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