# CVE-2022-42954: Cross-site scripting in n/a

> Cross-site scripting vulnerability in EJBCA allows attackers to execute arbitrary scripts in user browsers, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-w2vf-hmq9-55g6

## What is CVE-2022-42954?

CVE-2022-42954 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Keyfactor EJBCA before 7.10.0 allows XSS.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Keyfactor Kefactor Ejbca.

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

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

## Is CVE-2022-42954 being exploited?

There is no known exploitation of CVE-2022-42954 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42954 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-42954 in the wild and no public exploit code.

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-42954/ (Markdown: https://insights.sbomify.com/CVE-2022-42954/index.md)
```

## Sources

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

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