OAuth request forgery via missing state validation
Published Nov 14, 2022 · Updated Apr 30, 2025
CSRF in Concrete CMS before 8.5.10 and 9.0.0 through 9.1.2 allows remote attackers to submit forged core OAuth requests. The external Concrete authentication service neither adds nor verifies an OAuth state parameter, so requests are not bound to the initiating browser session. Exploitation requires user interaction, the OAuth client secret, and a client without a redirect URL; the resulting action is undisclosed, and Concrete CMS states that the configuration is impossible in version 9.
Summary
What happened
CSRF in Concrete CMS before 8.5.10 and 9.0.0 through 9.1.2 allows remote attackers to submit forged core OAuth requests. The external Concrete authentication service neither adds nor verifies an OAuth state parameter, so requests are not bound to the initiating browser session. Exploitation requires user interaction, the OAuth client secret, and a client without a redirect URL; the resulting action is undisclosed, and Concrete CMS states that the configuration is impossible in version 9.
The record
- CVE
- CVE-2022-43693
- Published
- Nov 14, 2022
- Updated
- Apr 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record 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.
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