VulnerabilityPublished 23 Feb 2026Updated 25 Feb 2026

CVE-2026-3026: erzhongxmu JEEWMS · Server-Side Request Forgery

Affects erzhongxmu JEEWMSSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 23 Feb 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
erzhongxmuJEEWMS	Affected =3.7	Fixed in–
Mavenerzhongxmu/JEEWMS`pkg:maven/erzhongxmu/JEEWMS`Other threats	Affected =3.7	Fixed in–

CPE configurations (1)

cpe:2.3:a:jeewms:jeewms:*:*:*:*:*:*:*:*

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

AI-suggested

Given the lack of an official patch from the vendor, organizations should implement immediate compensating controls to mitigate the risk. These include: 1) Restrict outbound HTTP requests from the JEEWMS server to only trusted destinations using network-level controls such as firewall rules or proxy filtering to prevent arbitrary external or internal requests. 2) Implement input validation or web application firewall (WAF) rules to detect and block malicious payloads targeting the 'upfile' parameter, focusing on SSRF patterns such as requests to localhost, private IP ranges, or metadata service endpoints. 3) If feasible, disable or restrict the UEditor component or the specific getRemoteImage.jsp functionality until a patch is available. 4) Monitor logs for unusual outbound requests originating from the JEEWMS server, which may indicate exploitation attempts. 5) Conduct internal network segmentation to limit the impact of SSRF by isolating critical internal services from the application server. 6) Engage with the vendor for updates and consider alternative software solutions if the vendor remains unresponsive. These measures collectively reduce the attack surface and limit potential damage from exploitation.

Description

A vulnerability has been found in erzhongxmu JEEWMS 3.7. Affected by this issue is some unknown functionality of the file /plug-in/ueditor/jsp/getRemoteImage.jsp of the component UEditor. The manipulation of the argument upfile leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SSRF vulnerability in JEEWMS 3.7 can have significant impacts on organizations using this software. Attackers can leverage this flaw to make unauthorized requests from the vulnerable server to internal systems that are otherwise inaccessible externally, potentially exposing sensitive internal services, metadata endpoints, or administrative interfaces. This can lead to information disclosure, unauthorized access, or serve as a pivot point for further attacks within the network. Since the vulnerability requires no authentication and no user interaction, it can be exploited remotely by unauthenticated attackers, increasing the risk of widespread exploitation. The absence of a vendor patch exacerbates the threat, leaving organizations exposed. The impact is particularly critical for organizations with sensitive internal infrastructure or those relying heavily on JEEWMS for critical operations. While no active exploitation is currently reported, the public availability of exploit details may lead to future attacks.

References

Community reviews

Loading reviews…