CVE-2023-7260 is a path traversal flaw in OpenText CX-E Voice that can let an attacker read arbitrary files on the system. It affects all versions through 22.4 and scores 7.5 (High). The record does not name a fixed version, so check the OpenText advisory.
What's affected
Affected: all versions of OpenText CX-E Voice through 22.4, per the record.
Fixed: not stated. I could not load the vendor article (KB0823114), so I cannot confirm a fixed release. Contact OpenText support or read the article for the corrected version.
The weakness is CWE-22, path traversal. The vector is network reachable, no privileges, no user interaction, and the impact is high confidentiality only, which means file reading and not modification. KEV is false and no source I read describes exploitation in the wild.
How to check if you're exposed
Check the CX-E Voice version in your deployment records or administration console. Anything at 22.4 or earlier is affected.
Then check exposure. Telephony and voice platforms are often reachable from several networks. Find out which of them can reach the web interface of the service.
What to do now
- Read the OpenText advisory and upgrade to the version it names.
- Restrict network access to the service to the systems and staff who need it.
- Look in web logs for requests with unusual path sequences.
- Rotate any credentials, keys or certificates stored on the host that a file read could have exposed.
Why it matters
A file read flaw is not an execution flaw, but it often leads there. Configuration files, credentials and private keys are all files. Reading one can give an attacker the access to do the rest.
That is why the high confidentiality rating deserves attention on voice platforms, which often hold call records and integration secrets.
Since the record does not name a fix, the first job is information gathering. Open the OpenText article, note the version it names, and check whether your support contract covers the upgrade. In the meantime, treat the host as one where files can be read by someone on the network, and decide what would hurt most if it leaked.
Good interim controls are simple. Put the service behind a firewall that allows only the systems that need it. Run it as a low privilege account so that a file read cannot reach system files. Keep secrets out of plain configuration files where the product allows it. And enable access logging, so that a probing request shows up on your side before it becomes an incident.
Quick check
Is there a fixed version of CX-E Voice?
The record does not name one. Check OpenText's advisory or ask support.
Can the attacker change files?
The vector rates confidentiality only. No integrity impact is scored.
Sources
Last reviewed: 19 October 2026.
