CVE-2025-8997: OpenText Enterprise Security Manager · Use of GET Request Method With Sensitive Query Strings
Affects OpenText Enterprise Security ManagerSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenText OpenText Enterprise Security Manager | Affected
| Fixed in– |
AI-suggested
European organizations should immediately review their use of OpenText Enterprise Security Manager to identify any instances where sensitive data is transmitted via GET requests. Specific mitigation steps include: 1) Configuring the application or web server to avoid placing sensitive information in URL query strings; instead, use POST requests or secure headers for transmitting confidential data. 2) Implementing strict access controls and monitoring to detect unusual access patterns or data exfiltration attempts. 3) Employing network-level protections such as TLS encryption to prevent interception of HTTP traffic, ensuring that all communications with the Enterprise Security Manager are over HTTPS. 4) Conducting user awareness training to reduce the risk of social engineering attacks that could trigger user interaction exploitation. 5) Monitoring vendor communications for patches or updates addressing this vulnerability and applying them promptly once available. 6) Reviewing and limiting logging configurations to avoid storing sensitive query strings in logs or caches. 7) Utilizing web application firewalls (WAFs) to detect and block suspicious GET requests containing sensitive parameters. These targeted actions go beyond generic advice by focusing on the specific nature of CWE-598 and the operational context of the affected product.
Description
An Information Exposure vulnerability has been identified in OpenText Enterprise Security Manager. The vulnerability could be remotely exploited.