GHSA-qrmm-w75w-3wpx: Server side request forgery in SwaggerUI
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: swagger-ui (npm) 4.1.3; swagger-ui-dist (npm) 4.1.3; swagger-ui-react (npm) 4.1.3.
Low priority for now. Upgrade to swagger-ui (npm) 4.1.3; swagger-ui-dist (npm) 4.1.3; swagger-ui-react (npm) 4.1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
SwaggerUI supports displaying remote OpenAPI definitions through the `?url` parameter. This enables robust demonstration capabilities on sites like `petstore.swagger.io`, `editor.swagger.io`, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered. However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances. An example scenario abusing this functionality could take the following form: - `https://example.com/api-docs` hosts a version of SwaggerUI with `?url=` query parameter enabled. - Users will trust the domain `https://example.com` and the contents of the OpenAPI definition. - A malicious actor may craft a similar OpenAPI definition and service that responds to the defined APIs at `https://evildomain`. - Users mistakenly click a phishing URL like `https://example.com/api-docs?url=https://evildomain/fakeapi.yaml` and enters sensitive data via the "Try-it-out" feature. We do want to stress that this attack vector is limited to scenarios that actively trick users into divulging sensitive information. The ease of this is highly contextual and, therefore, the threat model may be different for individual users and organizations. It is *not* possible to perform non-interactive attacks (e.g., cross-site scripting or code injection) through this mechanism. ### Resolution We've made the decision to [disable query parameters (#4872)](https://github.com/swagger-api/swagger-ui/issues/4872) by default starting with SwaggerUI version `4.1.3`. Please update to this version when it becomes available (**ETA: 2021 December**). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites. ### Workaround If you host a version of SwaggerUI and wish to mitigate this issue immediately, you are encouraged to add the following custom plugin code: ```js SwaggerUI({ // ...other configuration options, plugins: [function UrlParamDisablePlugin() { return { statePlugins: { spec: { wrapActions: { // Remove the ?url parameter from loading an external OpenAPI definition. updateUrl: (oriAction) => (payload) => { const url = new URL(window.location.href) if (url.searchParams.has('url')) { url.searchParams.delete('url') window.location.replace(url.toString()) } return oriAction(payload) } } } } } }], }) ``` ### Future UX work Through the exploration of this issue, it became apparent that users may not be aware to which web server the Try-it-out function will send requests. While this information is currently presented at the top of the page, understanding may improve by displaying it closer to the "Execute" button where requests are actually made. We'll be exploring these UX improvements over the coming months and welcome community input. Please create a Feature Request under the GitHub Issue tab to start a conversation with us and the community. ## Reflected XSS attack **Warning** in versions < 3.38.0, it is possible to combine the URL options (as mentioned above) with a vulnerability in DOMPurify (https://www.cvedetails.com/cve/CVE-2020-26870/) to create a reflected XSS vector. If your version of Swagger UI is older than 3.38.0, we suggest you upgrade or implement the workaround as mentioned above.
- Published
- Dec 9, 2021
- Updated
- Sep 10, 2026
- EPSS
- —
- CWE
- CWE-918
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| npm | swagger-ui | pkg:npm/swagger-ui |
| npm | swagger-ui-dist | pkg:npm/swagger-ui-dist |
| npm | swagger-ui-react | pkg:npm/swagger-ui-react |
| NuGet | Swashbuckle.AspNetCore.SwaggerUI | pkg:nuget/Swashbuckle.AspNetCore.SwaggerUI |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | swagger-ui | before 4.1.3 | 4.1.3 |
| npm | swagger-ui-dist | before 4.1.3 | 4.1.3 |
| npm | swagger-ui-react | before 4.1.3 | 4.1.3 |
| NuGet | Swashbuckle.AspNetCore.SwaggerUI | before 6.3.0 | 6.3.0 |
Same product
npm: all recordsOther highest-scoring records for the same primary product.
- GHSA-388g-jwpg-x6j4Cross-Site Scripting in swagger-ui26Monitor
- GHSA-4f9m-pxwh-68hgCross-Site Scripting in swagger-ui26Monitor
- GHSA-x9p2-fxq6-2m5fReverse Tabnapping in swagger-ui17Monitor
Published before and after this one in the same product
- ← EarlierGHSA-vp93-gcx5-4w52Sep 11, 2020 · Cross-Site Scripting in swagger-ui0Monitor
- ← EarlierGHSA-22q9-hqm5-mhmcSep 11, 2020 · Cross-Site Scripting in swagger-ui0Monitor
- ← EarlierGHSA-w992-2gmj-9xxjSep 11, 2020 · Cross-Site Scripting in swagger-ui0Monitor
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 |
|---|---|---|
| npm:swagger-ui | 4.1.3 | Package registry (OSV) |
| npm:swagger-ui-dist | 4.1.3 | Package registry (OSV) |
| npm:swagger-ui-react | 4.1.3 | Package registry (OSV) |
| NuGet:Swashbuckle.AspNetCore.SwaggerUI | 6.3.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- Fix✗ → ✓
- CVSS5.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.