CVE-2019-17495 — swagger-ui
CRITICALCVE-2019-17495 is a critical-severity (CVSS 9.8) Cross-Site Request Forgery (CSRF) vulnerability in org.webjars:swagger-ui. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.webjars:swagger-ui — see the affected versions and patch details below.
Cross-site scripting in Swagger-UI
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-17495 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.webjars:swagger-ui☕org.webjars.npm:swagger-ui☕io.springfox:springfox-swagger-ui📦swagger-uiReal-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
A Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO) technique to perform CSS-based input field value exfiltration, such as exfiltration of a CSRF token value. In other words, this product intentionally allows the embedding of untrusted JSON data from remote servers, but it was not previously known that <style>@import within the JSON data was a functional attack method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars:swagger-ui | all versions | 3.23.11org.webjars:swagger-ui:3.23.11 |
| ☕Maven | org.webjars.npm:swagger-ui | all versions | 3.23.11org.webjars.npm:swagger-ui:3.23.11 |
| ☕Maven | io.springfox:springfox-swagger-ui | all versions | 2.10.0io.springfox:springfox-swagger-ui:2.10.0 |
| 📦npm | swagger-ui | all versions | 3.23.11npm install swagger-ui@3.23.11 |
Research 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.webjars:swagger-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars:swagger-ui to 3.23.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17495 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-17495 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-17495. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-17495 in your dependencies?
O3 Security finds CVE-2019-17495 across Maven, npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.