Reflected script execution via unsanitized deviceId
Published May 18, 2020 · Updated Aug 4, 2024
Reflected XSS in rConfig 3.9.4 allows remote authenticated users to execute JavaScript via the deviceId parameter. devicemgmnt.php returns the deviceId GET value into an HTML response without sufficient validation, allowing injected script markup to run in the browser. A valid rConfig login and victim interaction with a crafted request are required, and execution occurs in the victim's rConfig browser context.
Summary
What happened
Reflected XSS in rConfig 3.9.4 allows remote authenticated users to execute JavaScript via the deviceId parameter. devicemgmnt.php returns the deviceId GET value into an HTML response without sufficient validation, allowing injected script markup to run in the browser. A valid rConfig login and victim interaction with a crafted request are required, and execution occurs in the victim's rConfig browser context.
The record
- CVE
- CVE-2020-12256
- Published
- May 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 2020CVE 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
- rConfig 3.9.4 deviceId reflected 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