VulnerabilityPublished 8 Mar 2026Updated 11 Mar 2026

CVE-2026-3743: 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, 06:59 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 29 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

Given the absence of an official patch, organizations should implement immediate compensating controls. First, restrict access to the YiFang CMS administrative interface by IP whitelisting or VPN to limit exposure. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the 'Name' parameter in the vulnerable update function. Educate administrators and content editors about the risk of phishing and social engineering attacks that could trigger the XSS payload. Regularly monitor CMS logs for unusual activity or unauthorized changes. If feasible, review and sanitize inputs at the application level by applying manual code fixes or input validation to neutralize script injection attempts. Consider isolating the CMS environment to reduce potential lateral movement in case of compromise. Stay alert for vendor updates or community patches and apply them promptly once available. Finally, implement Content Security Policy (CSP) headers to restrict script execution sources, mitigating the impact of XSS attacks.

Description

A flaw has been found in YiFang CMS 2.0.5. This affects the function update of the file app/db/admin/D_singlePageGroup.php. Executing a manipulation of the argument Name can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-3743 is the potential compromise of user sessions and unauthorized actions within the YiFang CMS administrative interface due to cross-site scripting. Attackers can leverage this vulnerability to steal cookies, hijack accounts, or perform actions on behalf of legitimate users, potentially leading to data leakage or unauthorized content modifications. For organizations relying on YiFang CMS 2.0.5, this could result in reputational damage, loss of data integrity, and increased risk of further exploitation if attackers gain administrative access. Since the vulnerability requires user interaction, phishing or social engineering campaigns could be used to trick administrators or editors into triggering the exploit. The lack of vendor response and patch availability prolongs exposure, increasing the window for attackers to develop and deploy exploits. While the vulnerability does not directly impact system availability, the indirect effects of compromised administrative accounts could lead to service disruptions or defacements.

Summary

CVE-2026-3743 is a cross-site scripting vulnerability identified in YiFang CMS version 2.0.5, specifically affecting the update function within the file app/db/admin/D_singlePageGroup.php. The vulnerability arises from insufficient input validation or sanitization of the 'Name' parameter, allowing an attacker to inject malicious scripts. When a victim user interacts with the manipulated input, the malicious script executes in their browser context, potentially leading to session hijacking, credential theft, or unauthorized actions within the CMS interface. The vulnerability is remotely exploitable without requiring authentication, but it does require user interaction to trigger the payload. The exploit code has been publicly released, increasing the risk of opportunistic attacks. The vendor was notified early but has not issued a patch or provided any response, leaving users exposed. The CVSS 4.0 score of 5.1 indicates a medium severity, with network attack vector, low attack complexity, no privileges required, and user interaction needed. The vulnerability impacts the confidentiality and integrity of user sessions but does not directly affect availability or system-level integrity. No mitigations or patches have been officially published, and no known active exploitation campaigns have been reported to date.

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