A Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO
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.
- Published
- Oct 10, 2019
- Updated
- Jun 16, 2026
- EPSS
- 5.7% · 93th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| smartbear | swagger ui | cpe:2.3:a:smartbear:swagger_ui |
| oracle | banking apis | cpe:2.3:a:oracle:banking_apis |
| oracle | banking digital experience | cpe:2.3:a:oracle:banking_digital_experience |
| oracle | banking platform | cpe:2.3:a:oracle:banking_platform |
| oracle | primavera gateway | cpe:2.3:a:oracle:primavera_gateway |
| oracle | utilities framework | cpe:2.3:a:oracle:utilities_framework |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oracle banking apis18.1 and later · up to 18.3 inclusive
- oracle banking apis19.1
- oracle banking apis19.2
- oracle banking apis20.1
- oracle banking apis21.1
- oracle banking digital experience18.1 and later · up to 18.3 inclusive
- oracle banking digital experience19.1
- oracle banking digital experience19.2
- oracle banking digital experience20.1
- oracle banking digital experience21.1
- oracle banking platform2.4.0 and later · up to 2.10.0 inclusive
- oracle primavera gateway16.2.0 and later · up to 16.2.11 inclusive
- oracle primavera gateway17.12.0 and later · up to 17.12.8 inclusive
- oracle utilities framework4.3.0.6.0
- oracle utilities framework4.4.0.0.0
- oracle utilities framework4.4.0.2.0
- smartbear swagger uibefore 3.23.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | io.springfox:springfox-swagger-ui | before 2.10.0 | 2.10.0 |
| Maven | org.webjars:swagger-ui | before 3.23.11 | 3.23.11 |
| Maven | org.webjars.npm:swagger-ui | before 3.23.11 | 3.23.11 |
| npm | swagger-ui | before 3.23.11 | 3.23.11 |
| npm | swagger-ui | before 3.23.11 | 3.23.11 |
Same product
smartbear: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-25031Swagger UI 4.1.2 and earlier could allow a remote attacker to conduct spoofing attacks.30Monitor
- CVE-2024-22207Default swagger-ui configuration exposes all files in the module22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:io.springfox:springfox-swagger-ui | 2.10.0 | Package registry (OSV) |
| Maven:org.webjars:swagger-ui | 3.23.11 | Package registry (OSV) |
| Maven:org.webjars.npm:swagger-ui | 3.23.11 | Package registry (OSV) |
| npm:swagger-ui | 3.23.11 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2019-12-24 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+74 d
- TodaySep 29, 2026+2546 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/swagger-api/swagger-ui/releases/tag/v3.23.11
- lists.apache.org/thread.html/r103579b01da2d0aa0f672b88f811224bbf8ef493aaad845895955e91%40%3Ccommits.airflow.apache.org%3E
- lists.apache.org/thread.html/r3acb7e494cf1aab99b6784b7c5bbddfd0d4f8a484ab534c3a61ef9cf%40%3Ccommits.airflow.apache.org%3E
- lists.apache.org/thread.html/r84b327f7a8b6b28857b906c07a66dd98e1d341191fa8d7816514ef96%40%3Ccommits.airflow.apache.org%3E
- lists.apache.org/thread.html/r853ffeb915a400f899de78124d4e0d77a19379d2e11bf8f4e98c624f%40%3Ccommits.airflow.apache.org%3E
- lists.apache.org/thread.html/ref70b940c4f69560d29d6ba792d6c82865e74de3dcad4c92d99b1f8f%40%3Ccommits.airflow.apache.org%3E
- www.oracle.com/security-alerts/cpuApr2021.html
- www.oracle.com/security-alerts/cpujan2022.html
- www.oracle.com/security-alerts/cpujul2022.html
- www.oracle.com/security-alerts/cpuoct2020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.