Unauthorized requests via exposed JavaScript CSRF token
Published Feb 9, 2022 · Updated Aug 3, 2024
Cross-site request forgery in Concrete CMS before 9.0.0 allows remote attackers to submit requests as other users through a malicious site. Affected releases place the CSRF token in dynamically generated JavaScript, allowing cross-origin retrieval and reuse in forged requests. Exploitation requires a victim's authenticated browser context; resulting requests carry that user's session authority and can perform any action reachable by that user.
Summary
What happened
Cross-site request forgery in Concrete CMS before 9.0.0 allows remote attackers to submit requests as other users through a malicious site. Affected releases place the CSRF token in dynamically generated JavaScript, allowing cross-origin retrieval and reuse in forged requests. Exploitation requires a victim's authenticated browser context; resulting requests carry that user's session authority and can perform any action reachable by that user.
The record
- CVE
- CVE-2021-22954
- Published
- Feb 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Concrete CMS
- Product
- Concrete CMS
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=fixed in Concrete CMS v 9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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