# CVE-2022-43670: XSS in Sling CMS Reference App Taxonomy Path

> An authenticated attacker can execute arbitrary scripts in the taxonomy management feature of Apache Sling CMS via reflected XSS.

- **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:** Yes
- **Published:** 2 Nov 2022
- **Updated:** 2 May 2025
- **Also known as:** GHSA-jj93-4jr5-x45h

## What is CVE-2022-43670?

CVE-2022-43670 is a medium-severity cross-site scripting vulnerability in Apache Sling App CMS, published on 2 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

An improper neutralization of input during web page generation ('Cross-site Scripting') [CWE-79] vulnerability in Sling App CMS version 1.1.0 and prior may allow an authenticated remote attacker to perform a reflected cross site scripting (XSS) attack in the taxonomy management feature.

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

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

2 open source packages ship an affected version, including org.apache.sling:org.apache.sling.cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.sling:org.apache.sling.cms` | Maven | All versions | 1.1.2 |
| `org.apache.sling:org.apache.sling.cms` | Maven | All versions | 1.1.2 |

Products: Apache Sling Cms.

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

Upgrade org.apache.sling:org.apache.sling.cms to 1.1.2 or later.

## Is CVE-2022-43670 being exploited?

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

## Other vulnerabilities in Apache Sling App CMS

- [CVE-2023-22849](https://insights.sbomify.com/CVE-2023-22849/): Apache Sling App CMS: XSS in CMS Reference / UI Components (medium 6.1)
- [CVE-2020-1949](https://insights.sbomify.com/CVE-2020-1949/): Cross-site scripting in Apache Sling (medium 6.1)
- [CVE-2022-46769](https://insights.sbomify.com/CVE-2022-46769/): Apache Sling App CMS: XSS in CMS Site Group Detail (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43670 is a medium-severity cross-site scripting vulnerability in Apache Sling App CMS, published on 2 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-43670 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.sling:org.apache.sling.cms (Maven): affected all versions; fixed in 1.1.2
- org.apache.sling:org.apache.sling.cms (Maven): affected all versions; fixed in 1.1.2

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

## Sources

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

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