VulnerabilityPublished 8 Mar 2026Updated 11 Mar 2026

CVE-2026-3742: YiFang CMS · Cross-site Scripting

Affects YiFang CMSSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 11:52 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 10% 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 8 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
YiFangCMS	Affected =2.0.5	Fixed in–
GitHubzzctd/CVE`pkg:github/zzctd/CVE`Other threats	Affected =2.0.5	Fixed in–

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

AI-suggested

Organizations should immediately implement input validation and output encoding for the Title parameter in the affected update function to prevent script injection. Until an official patch is released, applying web application firewall (WAF) rules to detect and block malicious payloads targeting the Title parameter is recommended. Restrict administrative access to trusted IP addresses and enforce multi-factor authentication to reduce the risk of exploitation. Regularly audit and monitor logs for suspicious activities related to page updates. Educate administrators about the risks of clicking on untrusted links or executing unverified scripts within the CMS interface. Consider isolating the CMS environment and limiting its exposure to the internet where feasible. Finally, maintain an active vulnerability management program to track updates from the vendor or community for any forthcoming patches.

Description

A vulnerability was detected in YiFang CMS 2.0.5. The impacted element is the function update of the file app/db/admin/D_singlePage.php. Performing a manipulation of the argument Title results in cross site scripting. It is possible to initiate the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The exploitation of this XSS vulnerability can lead to unauthorized script execution in the browsers of users interacting with the compromised CMS. This can result in session hijacking, defacement, phishing, or redirection to malicious sites, compromising user confidentiality and integrity of the web content. Although the vulnerability does not directly impact system availability, successful exploitation can damage organizational reputation and trust. Since the attack requires user interaction, the scope is somewhat limited, but the presence of public exploit code increases the risk of widespread attacks. Organizations relying on YiFang CMS 2.0.5 are at risk of targeted attacks, especially those with administrative users who may unknowingly trigger the exploit. The lack of vendor response and patch availability prolongs exposure, increasing the window for attackers to exploit this vulnerability.

Summary

CVE-2026-3742 is a cross-site scripting vulnerability identified in YiFang CMS version 2.0.5, specifically within the update function located in app/db/admin/D_singlePage.php. The vulnerability arises from improper sanitization or validation of the Title parameter, which can be manipulated by an attacker to inject malicious JavaScript code. This injection occurs when an administrator or authorized user updates a page title, allowing the malicious script to be stored and subsequently executed in the context of users viewing the affected page. The attack vector is remote and does not require prior authentication, though user interaction is necessary to trigger the exploit. The vulnerability has a CVSS 4.0 base score of 5.1, indicating medium severity, with characteristics including network attack vector, low attack complexity, no privileges required, but user interaction needed. The impact primarily affects confidentiality and integrity by enabling script execution that could hijack sessions, deface content, or conduct phishing attacks. The vendor was notified but has not issued a patch or response, and public exploit code is available, increasing the urgency for mitigation. No known exploits in the wild have been reported yet, but the public availability of exploit code raises the likelihood of future attacks. This vulnerability highlights the importance of input validation and output encoding in web applications, especially CMS platforms that are widely used for content management.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 09:07 UTC

Technical details

References

Community reviews

Related threats