# CVE-2022-45925: Information disclosure in n/a

> Attackers can obtain sensitive HTTP headers and CGI variables via the xmlexport action, exposing internal server details.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-2c9x-whr5-j4x3

## What is CVE-2022-45925?

CVE-2022-45925 is a high-severity vulnerability in n/a, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in OpenText Content Suite Platform 22.1 (16.2.19.1803). The action xmlexport accepts the parameter requestContext. If this parameter is present, the response includes most of the HTTP headers sent to the server and some of the CGI variables like remote_adde and server_name, which is an information disclosure.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-45925?

It affects 1 product.


Products: Opentext Opentext Extended Ecm.

## How do I fix CVE-2022-45925?

No fix has been published for CVE-2022-45925 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-45925 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45925 exists.

## Other vulnerabilities in n/a

- [CVE-2022-45922](https://insights.sbomify.com/CVE-2022-45922/): Auth bypass in n/a (high 8.8)
- [CVE-2022-45923](https://insights.sbomify.com/CVE-2022-45923/): Deserialization in n/a (high 8.8)
- [CVE-2022-45926](https://insights.sbomify.com/CVE-2022-45926/): Server-side request forgery in n/a (high 8.8)
- [CVE-2022-45927](https://insights.sbomify.com/CVE-2022-45927/): Auth bypass in n/a (high 8.8)
- [CVE-2022-45928](https://insights.sbomify.com/CVE-2022-45928/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45925 and fix it if it is affected.

What it is: CVE-2022-45925 is a high-severity vulnerability in n/a, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45925 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-45925/ (Markdown: https://insights.sbomify.com/CVE-2022-45925/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-45925
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-45925
- OSV: https://osv.dev/vulnerability/CVE-2022-45925

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-45925/
Summaries are generated and may contain mistakes; the official description above is the record.