Skip to content
Fencer Intel
critical 9.8

CVE-2019-17495 json

Cross-site scripting in Swagger-UI

published 7y ago modified 4mo ago also GHSA-c427-hjc3-wrfw , EUVD-2019-0696

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.7%
EPSS 5.7% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm swagger-ui 3.23.11
  • maven org.webjars:swagger-ui 3.23.11
  • maven org.webjars.npm:swagger-ui 3.23.11
  • maven io.springfox:springfox-swagger-ui 2.10.0
  • smartbear swagger_ui 3.23.11

Is CVE-2019-17495 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

5.73% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tarantula-team/CSS-injection-in-Swagger-UI referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm swagger-ui
<3.23.11
3.23.11
maven org.webjars:swagger-ui
<3.23.11
3.23.11
maven org.webjars.npm:swagger-ui
<3.23.11
3.23.11
maven io.springfox:springfox-swagger-ui
<2.10.0
2.10.0

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.