Unauthorized actions via forged trusted-user requests
Published Jun 18, 2025 · Updated Aug 24, 2025
Cross-site request forgery in IBM Sterling B2B Integrator allows remote attackers to execute unauthorized actions through a trusted user's browser. IBM has not published the affected request handler or identified the request-verification operation that fails. Exploitation requires user interaction and an authenticated, trusted session; successful requests perform unauthorized actions with that user's privileges.
Summary
What happened
Cross-site request forgery in IBM Sterling B2B Integrator allows remote attackers to execute unauthorized actions through a trusted user's browser. IBM has not published the affected request handler or identified the request-verification operation that fails. Exploitation requires user interaction and an authenticated, trusted session; successful requests perform unauthorized actions with that user's privileges.
The record
- CVE
- CVE-2024-54172
- Published
- Jun 18, 2025
- Updated
- Aug 24, 2025
- Vendor
- IBM
- Product
- IBM Sterling B2B Integrator
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 24, 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.0.0.0 <=6.1.2.6
- Affected versionversion=6.2.0.0 <=6.2.0.4
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