Sensitive-data disclosure via HTTP GET query strings
Published Mar 13, 2026 · Updated Mar 13, 2026
Information disclosure in IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 exposes sensitive query data. The application places sensitive request values in an HTTP GET URL query string instead of keeping them out of the request target. Exploitation requires an authenticated request and a man-in-the-middle position; the reported consequence is disclosure only.
Summary
What happened
Information disclosure in IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 exposes sensitive query data. The application places sensitive request values in an HTTP GET URL query string instead of keeping them out of the request target. Exploitation requires an authenticated request and a man-in-the-middle position; the reported consequence is disclosure only.
The record
- CVE
- CVE-2025-14811
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- OpenBMC Project
- Product
- IBM Sterling Partner Engagement Manager
- Classifications
- CWE-598, T1557
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record 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.2.3.0 <=6.2.3.5
- Affected versionversion=6.2.4.0 <=6.2.4.2
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