# CVE-2022-45928: Code injection in n/a

> Remote attackers can execute arbitrary Oscript code via the htmlFile parameter, leading to file manipulation, network connections, or OS command execution.

- **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-7qqq-mvm4-r635

## What is CVE-2022-45928?

CVE-2022-45928 is a high-severity code injection 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

A remote OScript execution issue was discovered in OpenText Content Suite Platform 22.1 (16.2.19.1803). Multiple endpoints allow the user to pass the parameter htmlFile, which is included in the HTML output rendering pipeline of a request. Because the Content Server evaluates and executes Oscript code in HTML files, it is possible for an attacker to execute Oscript code. The Oscript scripting language allows the attacker (for example) to manipulate files on the filesystem, create new network connections, or execute OS commands.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Opentext Opentext Extended Ecm.

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

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

## Is CVE-2022-45928 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45928 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-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-45928 and fix it if it is affected.

What it is: CVE-2022-45928 is a high-severity code injection 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-45928 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-45928/ (Markdown: https://insights.sbomify.com/CVE-2022-45928/index.md)
```

## Sources

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

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