# CVE-2025-8191: macrozheng mall Swagger UI index.html cross site scripting

> Remote attackers can execute arbitrary scripts via the Swagger UI configUrl parameter in macrozheng mall, potentially compromising user sessions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-cw4g-wcrm-x4x7

## What is CVE-2025-8191?

CVE-2025-8191 is a medium-severity cross-site scripting vulnerability in macrozheng mall, published on 26 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in macrozheng mall up to 1.0.3. Affected is an unknown function of the file /swagger-ui/index.html of the component Swagger UI. The manipulation of the argument configUrl leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor deleted the GitHub issue for this vulnerability without any explanation. Afterwards the vendor was contacted early about this disclosure via email but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-8191?

It affects 1 product.


Products: Macrozheng Mall.

## How do I fix CVE-2025-8191?

No fix has been published for CVE-2025-8191 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8191 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8191 exists.

Public exploit code:

- A repository containing a PoC exploit for CVE‑2025‑8191 in Swagger UI, leveraging XSS injection to exfiltrate session cookies. (github_poc): https://github.com/byteReaper77/CVE-2025-8191
- XSS Test Swagger  3.14.1 to 3.37.0 (github_poc): https://github.com/mayank-s16/Swagger-HTML-Injection-CVE-2025-8191
- Swagger UI 1.0.3 - Cross-Site Scripting (XSS) (exploitdb)
- https://github.com/YanC1e/CVE-2025-8191 (github_poc): https://github.com/YanC1e/CVE-2025-8191
- Testing for CVE-2025-8191 (github_poc): https://github.com/d154573r-4v3r73d/CVE-2025-8191

## Other vulnerabilities in macrozheng mall

- [CVE-2026-25858](https://insights.sbomify.com/CVE-2026-25858/): macrozheng mall <= 1.0.3 Unauthenticated Password Reset via OTP Disclosure (critical 9.3)
- [CVE-2025-8755](https://insights.sbomify.com/CVE-2025-8755/): macrozheng mall com.macro.mall.portal.controller UmsMemberController.java detail authorization (medium 6.9)
- [CVE-2025-9514](https://insights.sbomify.com/CVE-2025-9514/): macrozheng mall Registration weak password (medium 6.3)
- [CVE-2025-8741](https://insights.sbomify.com/CVE-2025-8741/): macrozheng mall login cleartext transmission (medium 6.3)
- [CVE-2025-8742](https://insights.sbomify.com/CVE-2025-8742/): macrozheng mall Admin Login excessive authentication (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8191 and fix it if it is affected.

What it is: CVE-2025-8191 is a medium-severity cross-site scripting vulnerability in macrozheng mall, published on 26 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8191 exists.

Affected product: macrozheng mall. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8191/ (Markdown: https://insights.sbomify.com/CVE-2025-8191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8191
- OSV: https://osv.dev/vulnerability/CVE-2025-8191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8191/
Summaries are generated and may contain mistakes; the official description above is the record.