VulnerabilityPublished 26 Jul 2025Updated 28 Jul 2025

CVE-2025-8191: macrozheng mall · Cross-site Scripting

Affects macrozheng mallSource CVE Database V5

Public exploit available (Exploit-DB) · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.7% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 26 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 8 days after disclosure
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
25 Jul 202508:54 UTC, 29 hours before disclosure
CVE published
on cve.org
26 Jul 202513:32 UTC, t = 0
In Threat Radar
record ingested
26 Jul 202513:47 UTC, 16 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
Swagger UI 1.0.3 - Cross-Site Scripting (XSS)
3 Aug 2025, 8 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmacrozheng/mall`pkg:github/macrozheng/mall`Other threats	Affected 1.0.0 – 1.0.3 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take immediate steps to mitigate this vulnerability. First, restrict access to the Swagger UI interface to trusted internal networks or authenticated users only, using network segmentation and access control lists. If possible, disable or remove the Swagger UI component from production environments where it is not essential. Employ web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting the 'configUrl' parameter. Implement strict Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. Monitor web server logs for suspicious requests targeting /swagger-ui/index.html and the 'configUrl' parameter. Finally, maintain user awareness training to recognize phishing or social engineering attempts that might leverage this vulnerability.

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.

Impact

For European organizations using macrozheng mall versions up to 1.0.3, this vulnerability poses a moderate risk. Since Swagger UI is often used for API documentation and testing, the exposure of this interface to external or internal users could allow attackers to execute malicious scripts, compromising user sessions or stealing sensitive information. This could lead to unauthorized access to backend systems or data breaches. The impact is heightened in sectors where API security is critical, such as finance, healthcare, and e-commerce, which are prevalent in Europe. Additionally, the vendor’s apparent lack of response and absence of patches increases the window of exposure. Organizations relying on this product without adequate compensating controls may face reputational damage, regulatory penalties under GDPR if personal data is compromised, and operational disruptions. The medium severity rating suggests that while the vulnerability is not critical, it should be addressed promptly to prevent exploitation.

Summary

CVE-2025-8191 is a cross-site scripting (XSS) vulnerability identified in the macrozheng mall product, versions 1.0.0 through 1.0.3. The vulnerability resides in the Swagger UI component, specifically within the /swagger-ui/index.html file. The issue arises due to improper sanitization or validation of the 'configUrl' argument, which can be manipulated by an attacker to inject malicious scripts. This vulnerability is remotely exploitable without requiring authentication, though it does require some user interaction (e.g., a victim visiting a crafted URL). The vulnerability has been publicly disclosed, and while no known exploits are currently observed in the wild, the exploit details are available, increasing the risk of future exploitation. The vendor’s lack of response and removal of the GitHub issue without explanation suggests a lack of timely patching or mitigation guidance. The CVSS 4.0 base score is 5.1, indicating a medium severity level, with attack vector being network-based, low attack complexity, no privileges required, but user interaction needed. The impact primarily affects the confidentiality and integrity of user sessions or data accessible via the vulnerable Swagger UI interface, potentially allowing attackers to execute arbitrary JavaScript in the context of the victim’s browser, leading to session hijacking, credential theft, or further attacks within the user’s session context.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Aug 2025, 01:00 UTC

Public exploits and detection1 Exploit-DB entry

Technical details

References

Community reviews

Related threats