CVE-2016-0712 — jetspeed
MEDIUMCVE-2016-0712 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.apache.portals.jetspeed-2:jetspeed. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.portals.jetspeed-2:jetspeed — see the affected versions and patch details below.
Cross-site Scripting in Apache Jetspeed
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.portals.jetspeed-2:jetspeedReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Cross-site scripting (XSS) vulnerability in Apache Jetspeed before 2.3.1 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to portal.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.portals.jetspeed-2:jetspeed | all versions | 2.3.1org.apache.portals.jetspeed-2:jetspeed:2.3.1 |
Affected Products
jetspeedapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.portals.jetspeed-2:jetspeed, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.portals.jetspeed-2:jetspeed to 2.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0712 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2016-0712 in your dependencies?
Find it across Maven, including transitive dependencies.