Stored XSS via unsanitized API nickname
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. Member.class.php's post() method stores the API nickname without filtering, and Author.class.php inserts it into page metadata and titles. The API must be enabled, an authenticated account must set the nickname, and another user must view that account's published articles.
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. Member.class.php's post() method stores the API nickname without filtering, and Author.class.php inserts it into page metadata and titles. The API must be enabled, an authenticated account must set the nickname, and another user must view that account's published articles.
The record
- CVE
- CVE-2021-37392
- Published
- Jul 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, CAPEC-592, 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 stored-XSS submission and trigger demonstrationproof 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