CVE-2025-14005VulnerabilityPublished 4 Dec 2025Updated 24 Feb 2026

CVE-2025-14005: dayrui XunRuiCMS · Cross Site Scripting

Affects dayrui XunRuiCMSSource 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 21% 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 4 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

Affected software

Product	Affected	Fixed in
GitHubdayrui/xunruicms`pkg:github/dayrui/xunruicms`Other threats	Affected =4.7.0 =4.7.1	Fixed in–

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

AI-suggested

1. Immediately restrict access to the administrative interface by IP whitelisting or VPN-only access to reduce exposure to remote attackers. 2. Implement web application firewall (WAF) rules to detect and block malicious payloads targeting the data[name] parameter in requests to /admind45f74adbd95.php. 3. Sanitize and validate all user inputs on the server side, especially the data[name] parameter, to prevent script injection. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the administrator’s browser. 5. Monitor logs for suspicious requests targeting the vulnerable endpoint and unusual administrator session activity. 6. If possible, disable or remove the Add Display Name Field functionality temporarily until a vendor patch is available. 7. Engage with the vendor or community to encourage the release of an official patch or update. 8. Educate administrators to be cautious of phishing or social engineering attempts that could trigger the XSS payload. 9. Regularly back up CMS data and configurations to enable recovery in case of compromise. These steps go beyond generic advice by focusing on access control, input validation, and layered defenses specific to the vulnerable component and attack vector.

Description

A weakness has been identified in dayrui XunRuiCMS up to 4.7.1. Affected by this vulnerability is an unknown functionality of the file /admind45f74adbd95.php?c=field&m=add&rname=site&rid=1&page=0 of the component Add Display Name Field. Executing a manipulation of the argument data[name] can lead to cross site scripting. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2025-14005 is the potential for attackers to execute arbitrary scripts in the context of an administrator’s browser session, leading to session hijacking, credential theft, or unauthorized actions within the CMS. This can result in defacement of websites, unauthorized content changes, or further compromise of the underlying server if combined with other vulnerabilities. Organizations relying on XunRuiCMS for content management may face reputational damage, data integrity issues, and operational disruptions. Since the vulnerability can be exploited remotely and does not require authentication, attackers can target exposed administrative interfaces over the internet. The public availability of exploit code increases the risk of widespread attacks, especially against organizations that have not applied mitigations or workarounds. The lack of vendor response and absence of official patches prolong the exposure window, making timely mitigation critical. Overall, the vulnerability threatens the confidentiality and integrity of administrative sessions and the availability of the CMS-managed content.

Summary

CVE-2025-14005 is a medium severity cross-site scripting vulnerability found in dayrui XunRuiCMS versions up to 4.7.1. The vulnerability resides in the Add Display Name Field feature, specifically within the /admind45f74adbd95.php file, which handles requests to add fields. By manipulating the data[name] parameter, an attacker can inject malicious JavaScript code that executes in the context of an authenticated administrator’s browser session. The attack vector is remote and does not require prior authentication, but user interaction is necessary to trigger the malicious payload. The vulnerability arises from insufficient input validation or output encoding of the data[name] parameter, allowing script injection. The vendor was notified early but has not issued a patch or response, and no official remediation is currently available. Public exploit code has been released, increasing the likelihood of exploitation attempts. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H indicates high privileges required, but the description suggests no authentication is needed, so this may be a discrepancy), user interaction required (UI:P), and limited impact on confidentiality and integrity. This vulnerability primarily threatens the integrity of the administrator’s session and the availability of the CMS interface through potential defacement or session hijacking. Given the lack of vendor response and public exploit availability, this vulnerability poses a tangible risk to organizations using XunRuiCMS versions 4.7.0 and 4.7.1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:47 UTC

Technical details

References

Community reviews

Related threats