CVE-2018-25031

Swagger UI 4.1.2 and earlier could allow a remote attacker to conduct spoofing attacks. By persuading a victim to open a crafted URL, an attacker could exploit this vulnerability to display remote OpenAPI definitions. Note: This was originally claimed to be resolved in 4.1.3. However, third parties have indicated this is not resolved in 4.1.3 and even occurs in that version and possibly others.

CVSS: 4.3Mediumscored by CISA
Exploited in the wild: Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS: 42.3%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 11 Mar 2022analysed here 12 Nov 2026

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weaknesses: CWE-20 Improper Input Validation
CWE-918 Server-Side Request Forgery (SSRF)
CWE-922 Common Weakness
Can a WAF block it?: Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

smartbear:swagger_ui

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. SSRF makes the server call a URL the attacker picks. A WAF can block well-known targets such as cloud metadata addresses, but not every internal host.

Also consider: egress filter · IMDSv2

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Not listed as of our last sync.
Public exploit code: Unvetted proof-of-concept code on GitHub: 15 GitHub proofs of concept
CISA SSVC: exploitation poc, automatable no, technical impact partialAssessed by CISA 18 Jul 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

mathis2001/CVE-2018-250313 stars
afine-com/CVE-2018-250312 stars
rafaelcintralopes/SwaggerUI-CVE-2018-250312 stars
LUCASRENAA/CVE-2018-250310 stars

and 11 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

11 Mar 2022Published
26 May 2022First proof-of-concept repository on GitHub (unvetted)76 days (about 3 months) later
18 Jul 2024CISA SSVC assessment: exploitation poc785 days (about 2 years) later
5 Aug 2024CVE record last updated18 days later
12 Nov 2026Analysed by vulneraibility.com829 days (about 2 years) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	RequiredA victim must click, open or otherwise cooperate.	A victim must click, open or otherwise cooperate.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	LowPartial data disclosure.	Partial data disclosure.
Integrity	NoneNo unauthorised modification.	No unauthorised modification.
Availability	NoneThe service stays up.	The service stays up.

Common questions

Is CVE-2018-25031 being exploited?

Not confirmed. CVE-2018-25031 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 42% probability of exploitation in the next 30 days.

How severe is CVE-2018-25031?

CVE-2018-25031 is rated Medium with a CVSS score of 4.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2018-25031?

Yes. A fix has been recorded for CVE-2018-25031. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2018-25031 affect?

CVE-2018-25031 affects smartbear:swagger_ui. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

4 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.