# CVE-2019-10076: Cross-Site Scripting in JSPWiki

> Attackers can execute arbitrary scripts via malicious attachments in Apache JSPWiki, leading to session hijacking.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cxx2-fp39-rf3r

## What is CVE-2019-10076?

CVE-2019-10076 is a medium-severity cross-site scripting vulnerability in Apache JSPWiki, published on 20 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A carefully crafted malicious attachment could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.

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

## Which versions are affected by CVE-2019-10076?

4 open source packages ship an affected version, including org.apache.jspwiki:jspwiki-main and org.apache.jspwiki:jspwiki-war. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.jspwiki:jspwiki-main` | Maven | From 2.9.0 | 2.11.0.M4 |
| `org.apache.jspwiki:jspwiki-main` | Maven | From 2.9.0 | 2.11.0.M4 |
| `org.apache.jspwiki:jspwiki-war` | Maven | From 2.9.0 | 2.11.0.M4 |
| `org.apache.jspwiki:jspwiki-war` | Maven | From 2.9.0 | 2.11.0.M4 |

Products: Apache Jspwiki.

## How do I fix CVE-2019-10076?

Upgrade org.apache.jspwiki:jspwiki-main to 2.11.0.M4 or later.

## Is CVE-2019-10076 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/apache__jspwiki_CVE-2019-10076_2-11-0-M3 (github_poc): https://github.com/shoucheng3/apache__jspwiki_CVE-2019-10076_2-11-0-M3

## Other vulnerabilities in Apache JSPWiki

- [CVE-2026-28812](https://insights.sbomify.com/CVE-2026-28812/): Apache JSPWiki: UserManager does not sanity-check user database at startup (critical 9.8)
- [CVE-2021-44140](https://insights.sbomify.com/CVE-2021-44140/): Arbitrary file deletion on logout (critical 9.1)
- [CVE-2026-28813](https://insights.sbomify.com/CVE-2026-28813/): Apache JSPWiki: JSPWiki vulnerable to JSON hijacking (high 8.8)
- [CVE-2022-34158](https://insights.sbomify.com/CVE-2022-34158/): User Group Privilege Escalation (high 8.8)
- [CVE-2022-24947](https://insights.sbomify.com/CVE-2022-24947/): Apache JSPWiki CSRF Account Takeover (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10076 and fix it if it is affected.

What it is: CVE-2019-10076 is a medium-severity cross-site scripting vulnerability in Apache JSPWiki, published on 20 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10076 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.jspwiki:jspwiki-main (Maven): affected from 2.9.0; fixed in 2.11.0.M4
- org.apache.jspwiki:jspwiki-main (Maven): affected from 2.9.0; fixed in 2.11.0.M4
- org.apache.jspwiki:jspwiki-war (Maven): affected from 2.9.0; fixed in 2.11.0.M4
- org.apache.jspwiki:jspwiki-war (Maven): affected from 2.9.0; fixed in 2.11.0.M4

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

## Sources

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

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