# CVE-2022-4523: vexim2 cross site scripting

> Remote attackers can execute arbitrary scripts in victim browsers via cross-site scripting in vexim2, potentially leading to session hijacking.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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:** 15 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hhvv-m62h-5c8j

## What is CVE-2022-4523?

CVE-2022-4523 is a low-severity cross-site scripting vulnerability in unspecified vexim2, published on 15 Dec 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

A vulnerability, which was classified as problematic, has been found in vexim2. This issue affects some unknown processing. The manipulation leads to cross site scripting. The attack may be initiated remotely. The name of the patch is 21c0a60d12e9d587f905cd084b2c70f9b1592065. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-215903.

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

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

It affects 1 product.


Products: Virtual Exim Project Virtual Exim 2.

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

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

## Is CVE-2022-4523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4523 is a low-severity cross-site scripting vulnerability in unspecified vexim2, published on 15 Dec 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-4523 in the wild and no public exploit code.

Affected product: unspecified vexim2. 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-4523/ (Markdown: https://insights.sbomify.com/CVE-2022-4523/index.md)
```

## Sources

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

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