# CVE-2022-45926: Server-side request forgery in n/a

> A low-privilege user can exploit the notify.localizeEmailTemplate endpoint to evaluate webreports, potentially leading to server-side request forgery and data access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-9pwg-jcxf-3vjr

## What is CVE-2022-45926?

CVE-2022-45926 is a high-severity server-side request forgery vulnerability in n/a, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in OpenText Content Suite Platform 22.1 (16.2.19.1803). The endpoint notify.localizeEmailTemplate allows a low-privilege user to evaluate webreports.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Opentext Opentext Extended Ecm.

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

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

## Is CVE-2022-45926 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45926 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-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)
- [CVE-2022-45924](https://insights.sbomify.com/CVE-2022-45924/): Missing authorization in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45926 is a high-severity server-side request forgery vulnerability in n/a, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45926 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-45926/ (Markdown: https://insights.sbomify.com/CVE-2022-45926/index.md)
```

## Sources

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

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