CVE-2018-25031

This repository provides a proof-of-concept for CVE-2018-25031, a spoofing vulnerability in Swagger UI before 4.1.3. The exploit involves crafting URLs with 'configUrl' or 'url' parameters to display remote OpenAPI definitions, potentially leading to phishing or misinformation attacks.

This PoC demonstrates an OpenAPI definition spoofing vulnerability in Swagger UI before 4.1.3. By crafting a URL with a malicious `configUrl` or `url` parameter, an attacker can display arbitrary remote OpenAPI definitions, potentially leading to phishing or misinformation attacks.

This PoC checks for CVE-2018-25031 in Swagger UI by testing if external URLs can be loaded via `configUrl` or `url` parameters, indicating potential UI misrepresentation. It uses Selenium to automate browser interactions and logs network requests to detect vulnerability.

The repository contains functional exploit code demonstrating XSS vulnerabilities in DOMPurify via crafted OpenAPI/Swagger YAML files. The payloads include various XSS vectors embedded in API documentation descriptions, targeting CVE-2018-25031.

The repository contains a YAML file with a Swagger API documentation that includes a login form pointing to an external IP address. There is no actual exploit code or technical details about CVE-2018-25031, making it appear as a potential lure for further interaction.

The repository provides a detailed writeup and proof-of-concept for CVE-2018-25031, a vulnerability in Swagger UI that allows remote specification loading, leading to potential HTML injection, XSS, and SSRF attacks.

This repository contains a YAML file demonstrating an XSS vulnerability in Swagger UI (CVE-2018-25031) via crafted API documentation. The payload injects malicious JavaScript into the description field, triggering an alert when rendered.

This repository contains functional proof-of-concept code for CVE-2018-25031, demonstrating a DOM-based XSS vulnerability. The exploit leverages malformed Swagger/OpenAPI documentation to inject malicious JavaScript payloads, triggering XSS in vulnerable systems.

The repository contains only a minimal OpenAPI YAML file with no functional exploit code or technical details about CVE-2018-25031. It lacks any meaningful content to demonstrate or analyze the vulnerability.

The repository contains only a minimal YAML file with a title and description mentioning SSRF (CVE-2018-25031) but lacks any functional exploit code or technical details.

The repository contains a minimal OpenAPI YAML file with placeholder text and no functional exploit code. It lacks technical details or executable payloads related to CVE-2018-25031.

This PoC exploits CVE-2018-25031 in Swagger UI before 4.1.3 by tricking victims into entering an authorization code, which is then exfiltrated to an attacker-controlled URL. It leverages XSS via malicious configUrl or url parameters to capture sensitive data.

The repository contains YAML files demonstrating an XSS vulnerability in Swagger UI by embedding malicious HTML/JavaScript payloads in API descriptions. The payloads attempt to steal cookies via an onerror event in an img tag.

The repository contains only a README.md file with minimal information about CVE-2018-25031, lacking any actual exploit code or technical details. No proof-of-concept or exploit implementation is provided.

This repository contains a Python-based PoC for CVE-2018-25031, demonstrating a Cross-Site Scripting (XSS) vulnerability in Swagger UI versions 2.9.2 and earlier. The script uses Selenium to automate testing of target URLs by injecting a malicious payload via the `configUrl` parameter.