CVE-2025-15149VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15149: rawchen ecms · Cross Site Scripting

Affects rawchen ecmsSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 28 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-26.

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

1. Implement strict input validation and sanitization on the productName parameter to reject or neutralize malicious scripts before processing. 2. Apply proper output encoding (e.g., HTML entity encoding) when rendering user-supplied data in the web interface to prevent script execution. 3. Restrict access to the Add New Product Page and related administrative interfaces using strong authentication and network segmentation. 4. Monitor logs and web traffic for suspicious input patterns or unusual activity related to product updates. 5. Employ Content Security Policy (CSP) headers to limit the impact of potential XSS by restricting script sources. 6. If possible, deploy a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the vulnerable parameter. 7. Engage with the vendor or community to obtain updates or patches and plan for timely application once available. 8. Educate administrators about the risks of clicking on suspicious links or entering untrusted data. 9. Consider isolating or sandboxing the ecms environment to limit potential lateral movement in case of compromise.

Description

A vulnerability has been found in rawchen ecms up to b59d7feaa9094234e8aa6c8c6b290621ca575ded. Affected by this vulnerability is the function updateProductServlet of the file src/servlet/product/updateProductServlet.java of the component Add New Product Page. The manipulation of the argument productName leads to cross site scripting. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of CVE-2025-15149 depends on their use of rawchen ecms, particularly in e-commerce or product catalog management. Successful exploitation could allow attackers to execute arbitrary scripts in the context of privileged users, potentially leading to unauthorized actions such as modifying product details, injecting malicious content, or conducting phishing attacks against administrators. While the vulnerability does not directly compromise confidentiality or availability, it undermines data integrity and could facilitate further attacks or social engineering. Organizations with public-facing admin portals are at higher risk, as attackers can remotely attempt exploitation. The lack of vendor response and patches increases exposure time, necessitating proactive defensive measures. Additionally, the presence of publicly disclosed exploit code raises the likelihood of opportunistic attacks targeting vulnerable systems in Europe.

Summary

CVE-2025-15149 identifies a cross-site scripting (XSS) vulnerability in the rawchen ecms content management system, specifically in the updateProductServlet.java file's updateProductServlet function. This vulnerability is triggered by manipulation of the productName parameter on the Add New Product Page, which lacks proper input sanitization and output encoding. As a result, an attacker can inject malicious JavaScript code that executes in the context of an administrator or user with privileges to update product information. The vulnerability is remotely exploitable without authentication but requires user interaction, such as an admin submitting a crafted product name. The CVSS 4.0 score of 4.8 reflects a medium severity, considering the attack vector is network-based with low attack complexity but requiring user interaction and privileges. The impact primarily affects data integrity by allowing script injection that could alter displayed content or perform unauthorized actions within the admin interface. Confidentiality and availability impacts are minimal or none. The vendor follows a rolling release model but has not responded to the vulnerability report, and no official patches or updates have been published. Public disclosure of the exploit code increases the risk of exploitation, especially in environments where rawchen ecms is used for e-commerce or product management. Organizations relying on this software should prioritize mitigation to prevent potential exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:10 UTC

Technical details

References

Community reviews

Related threats