Unauthorized state changes via missing CSRF tokens
Published Feb 27, 2025 · Updated Feb 27, 2025
CSRF in WSO2 Enterprise Integrator 6.6.0 allows remote attackers to change management-console state through an authenticated user's browser. A limited set of management-console operations performs state changes without validating a CSRF token, so forged cross-origin requests inherit the victim's session authority. Exploitation requires social engineering of a user with console access and is limited to unauthorized actions such as changing account settings or data.
Summary
What happened
CSRF in WSO2 Enterprise Integrator 6.6.0 allows remote attackers to change management-console state through an authenticated user's browser. A limited set of management-console operations performs state changes without validating a CSRF token, so forged cross-origin requests inherit the victim's session authority. Exploitation requires social engineering of a user with console access and is limited to unauthorized actions such as changing account settings or data.
The record
- CVE
- CVE-2024-0392
- Published
- Feb 27, 2025
- Updated
- Feb 27, 2025
- Vendor
- WSO2
- Product
- WSO2 Enterprise Integrator
- Classifications
- CWE-352, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Feb 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.6.0 <6.6.0.179
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.
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