# CVE-2022-4011: Simple History Plugin Header neutralization for logs

> Attackers can inject malicious content into logs via X-Forwarded-For headers, potentially leading to stored XSS or log poisoning in Simple History Plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-f39f-g3gv-88jq

## What is CVE-2022-4011?

CVE-2022-4011 is a medium-severity cross-site scripting vulnerability in unspecified Simple History Plugin, published on 16 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Simple History Plugin. It has been rated as critical. This issue affects some unknown processing of the component Header Handler. The manipulation of the argument X-Forwarded-For leads to improper output neutralization for logs. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-213785 was assigned to this vulnerability.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-707 (Improper Neutralization)

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

It affects 1 product.


Products: Simple History Project Simple History.

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

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

## Is CVE-2022-4011 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4011 is a medium-severity cross-site scripting vulnerability in unspecified Simple History Plugin, published on 16 Nov 2022. 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-4011 exists.

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

## Sources

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

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