Unauthorized state changes via defective CSRF token
Published Jan 19, 2024 · Updated Jun 17, 2025
Cross-site request forgery in IBM Maximo Asset Management 7.6.1.3 and Manage 8.10 through 8.11 allows remote attackers to submit unauthorized actions. IBM identifies the CSRF token as the affected locus but does not disclose which validation operation accepts an untrusted request. Exploitation requires an authenticated user to interact with attacker-controlled content, and the published impact is limited to unauthorized state changes.
Summary
What happened
Cross-site request forgery in IBM Maximo Asset Management 7.6.1.3 and Manage 8.10 through 8.11 allows remote attackers to submit unauthorized actions. IBM identifies the CSRF token as the affected locus but does not disclose which validation operation accepts an untrusted request. Exploitation requires an authenticated user to interact with attacker-controlled content, and the published impact is limited to unauthorized state changes.
The record
- CVE
- CVE-2023-47718
- Published
- Jan 19, 2024
- Updated
- Jun 17, 2025
- Vendor
- IBM
- Product
- IBM Maximo Asset Management
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=7.6.1.3
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