Script execution via unsanitized rcID reflection
Published Jan 14, 2020 · Updated Aug 6, 2024
Reflected XSS in Concrete CMS 5.4.1.1 and earlier allows remote attackers to execute script in a victim's browser via rcID. The unauthenticated do_login endpoint reflects the unsanitized rcID value into its HTML response, allowing attribute-breaking input to become executable markup. A victim must submit an attacker-controlled login request, after which the script runs in the site's browser origin.
Summary
What happened
Reflected XSS in Concrete CMS 5.4.1.1 and earlier allows remote attackers to execute script in a victim's browser via rcID. The unauthenticated do_login endpoint reflects the unsanitized rcID value into its HTML response, allowing attribute-breaking input to become executable markup. A victim must submit an attacker-controlled login request, after which the script runs in the site's browser origin.
The record
- CVE
- CVE-2011-3183
- Published
- Jan 14, 2020
- Updated
- Aug 6, 2024
- Vendor
- Concrete CMS
- Product
- Concrete CMS
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=through 5.4.1.1
What conditions does exploitation require?
What is affected?
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
- Concrete CMS rcID XSS proof of conceptproof 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