VulnerabilityPublished 9 Feb 2026Updated 23 Feb 2026

CVE-2026-2200: heyewei JFinalCMS · Cross-site Scripting

Affects heyewei JFinalCMSSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 14:05 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 18% 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 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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
heyeweiJFinalCMS	Affected =5.0.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:heyewei:jfinalcms:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2200, organizations should first verify if they are running heyewei JFinalCMS version 5.0.0 and restrict access to the /admin/admin/save endpoint to trusted administrative users only. Implement strict input validation and output encoding on all user-supplied data processed by this endpoint to prevent script injection. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the browser. Use multi-factor authentication (MFA) for administrative accounts to reduce the risk of credential compromise. Monitor administrative access logs for suspicious activity and implement network-level controls such as IP whitelisting or VPN access for administration. If vendor patches become available, apply them promptly. Until patches are released, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the vulnerable endpoint. Educate administrators about phishing and social engineering risks to minimize user interaction exploitation. Regularly audit and update CMS components to maintain security hygiene.

Description

A weakness has been identified in heyewei JFinalCMS 5.0.0. This affects an unknown function of the file /admin/admin/save of the component API Endpoint. Executing a manipulation can lead to cross site scripting. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The primary impact of CVE-2026-2200 is on the integrity and confidentiality of administrative sessions within JFinalCMS 5.0.0 environments. Successful exploitation can lead to execution of arbitrary scripts in the context of the administrator's browser, enabling session hijacking, credential theft, or unauthorized administrative actions. This can result in website defacement, data manipulation, or further compromise of backend systems. Since the vulnerability requires high privileges and user interaction, the risk is somewhat contained but still significant for organizations relying on JFinalCMS for critical web content management. Attackers could use this vector to pivot into deeper network layers or disrupt business operations by altering website content. The public availability of exploit code increases the likelihood of opportunistic attacks, especially against less vigilant or unpatched installations. Organizations with exposed administrative interfaces accessible over the internet are particularly vulnerable. The impact on availability is minimal, but the reputational damage and potential data breaches pose substantial risks.

Summary

CVE-2026-2200 identifies a cross-site scripting vulnerability in the heyewei JFinalCMS content management system, specifically version 5.0.0. The vulnerability resides in the /admin/admin/save API endpoint, which is part of the administrative interface. An attacker can craft malicious input that, when processed by this endpoint, results in the injection of executable scripts into the web application context. This XSS flaw can be exploited remotely but requires the attacker to have high privileges (PR:H) and some user interaction (UI:P), such as tricking an administrator into clicking a crafted link or submitting a malicious form. The vulnerability does not require authentication bypass but does require the attacker to have access to the administrative functions, limiting the attack surface. The CVSS vector indicates no impact on confidentiality (VC:N) or availability (VA:N), but a low impact on integrity (VI:L) due to script injection. The vulnerability is exploitable with low attack complexity (AC:L) and no scope change (S:U). Although no active exploits have been reported in the wild, the availability of proof-of-concept code increases the risk of future exploitation. The lack of official patches or mitigation guidance from the vendor at the time of publication necessitates proactive defensive measures by administrators. The vulnerability could be leveraged to hijack administrator sessions, perform unauthorized actions, or deface the CMS interface, undermining the trustworthiness of affected websites.

References

Community reviews

Loading reviews…