CVE-2025-15248VulnerabilityPublished 30 Dec 2025

CVE-2025-15248: sunhailin12315 product-review 商品评价系统 · Cross Site Scripting

Affects sunhailin12315 product-review 商品评价系统Source CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% 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

Disclosed: evidence found.
CVE published 30 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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

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 2026-10-25.

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 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

AI-suggested

Given the absence of an official patch, European organizations should implement immediate mitigations including: 1) Applying strict input validation and output encoding on the 'content' field in the review submission process to neutralize malicious scripts. 2) Deploying or tuning Web Application Firewalls (WAFs) to detect and block common XSS payloads targeting this component. 3) Implementing Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4) Conducting regular security audits and penetration testing focused on user input handling in the review system. 5) Monitoring logs for suspicious activities related to review submissions. 6) Engaging with the vendor or community to track patch releases or updates. 7) Educating users about the risks of clicking untrusted links and encouraging cautious behavior. 8) Considering temporary disabling or restricting the review submission feature if feasible until a patch is available.

Description

A security flaw has been discovered in sunhailin12315 product-review 商品评价系统 up to 91ead6890b4065bb45b7602d0d73348e75cb4639. This affects an unknown part of the component Write a Review. Performing manipulation of the argument content results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been released to the public and may be exploited. This product adopts a rolling release strategy to maintain continuous delivery The project was informed of the problem early through an issue report but has not responded yet.

Impact

For European organizations, the impact of this XSS vulnerability includes potential compromise of user sessions, theft of sensitive information such as cookies or credentials, and manipulation or defacement of product reviews. This can damage brand reputation, reduce customer trust, and potentially lead to further attacks if attackers leverage stolen session tokens to escalate privileges. E-commerce platforms and businesses relying on user-generated content are particularly at risk. The vulnerability could also facilitate phishing attacks by injecting malicious scripts that redirect users to fraudulent sites. While the direct impact on system availability is low, the integrity and confidentiality of user data are at risk. Organizations failing to address this vulnerability may face regulatory scrutiny under GDPR if personal data is compromised. The public availability of exploit code increases the risk of opportunistic attacks, especially against less-secured or unpatched deployments.

Summary

CVE-2025-15248 is a cross-site scripting vulnerability discovered in the sunhailin12315 product-review 商品评价系统, a system used for managing product reviews. The vulnerability resides in the 'Write a Review' component, where the 'content' argument is insufficiently sanitized, allowing attackers to inject malicious JavaScript code. This flaw can be exploited remotely without authentication but requires user interaction, such as a victim clicking a crafted link or visiting a malicious page. The vulnerability is present up to the specific commit version 91ead6890b4065bb45b7602d0d73348e75cb4639. The product uses a rolling release strategy, but the vendor has not yet responded to the issue report or released a patch. The CVSS 4.0 base score is 5.1 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, but user interaction needed, and limited impact on confidentiality and integrity. Public exploit code has been released, increasing the likelihood of exploitation. The vulnerability could lead to session hijacking, credential theft, or defacement of the review system, undermining user trust and data integrity. No known exploits in the wild have been reported yet, but the availability of proof-of-concept code raises concern. The lack of vendor response and patch availability means organizations must implement interim mitigations.

References

Community reviews

Loading reviews…