Skip to main content
VulnerabilityPublished

CVE-2025-8716: OpenText Content Management · Unchecked Error Condition

Affects OpenText Content ManagementSource CVE Database V5

0

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
OpenText OpenText Content ManagementAffected
  • =20.4-25.3
Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately review and restrict access controls within OpenText Content Management to ensure that only necessary users have authenticated access, minimizing the attack surface. 2) Implement strict monitoring and logging of file access and cache behavior to detect unusual patterns indicative of cache poisoning attempts. 3) Conduct thorough audits of file permissions and ensure that sensitive files are properly protected and not inadvertently exposed via caching mechanisms. 4) Employ multi-factor authentication (MFA) to reduce the risk of credential compromise that could enable exploitation. 5) Engage with OpenText support channels to obtain any forthcoming patches or workarounds and apply them promptly once available. 6) Consider network segmentation and application-layer firewalls to limit access to the content management system from untrusted networks. 7) Educate users about phishing and social engineering risks that could lead to credential theft and subsequent exploitation of this vulnerability. These steps go beyond generic advice by focusing on access control tightening, proactive monitoring of cache behavior, and user credential protection specific to the nature of this vulnerability.

Description

In Content Management versions 20.4- 25.3 authenticated attackers may exploit a complex cache poisoning technique to download unprotected files from the server if the filenames are known.

References

Community reviews

Loading reviews…