VulnerabilityPublished 2 Mar 2026

CVE-2026-3405: thinkgem JeeSite · Path Traversal

Affects thinkgem JeeSiteSource CVE Database V5

Compare

Public exploit available · CVSS 2.3 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

2.3Low

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: 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: None: There is no loss of integrity within 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 2 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
thinkgemJeeSite	Affected =5.15.0 =5.15.1	Fixed in–
Maventhinkgem/JeeSite`pkg:maven/thinkgem/JeeSite`Other threats	Affected =5.15.0 =5.15.1	Fixed in–

CPE configurations (1)

cpe:2.3:a:jeesite:jeesite:*:*:*:*:*:*:*:*

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

AI-suggested

To mitigate CVE-2026-3405, organizations should first identify all instances of JeeSite 5.15.0 and 5.15.1 in their environment and restrict external access to the affected Connection Handler component where possible. Employ network segmentation and firewall rules to limit exposure. Conduct thorough input validation and sanitization on all user-supplied data related to file paths within custom code interfacing with JeeSite. Monitor logs for suspicious access attempts indicative of path traversal exploitation. Consider deploying runtime application self-protection (RASP) solutions to detect and prevent exploitation attempts in real time. Engage with the vendor or community for updates and patches, and plan for an upgrade once a fix is released. Additionally, conduct regular security assessments and penetration tests focusing on file path handling to identify similar weaknesses.

Description

A vulnerability has been found in thinkgem JeeSite up to 5.15.1. The affected element is an unknown function of the component Connection Handler. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is described as difficult. 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 primary impact of CVE-2026-3405 is unauthorized disclosure of sensitive information due to path traversal, which can expose configuration files, source code, or other critical data stored on the server. This can lead to further exploitation, such as credential theft or system reconnaissance. However, the high complexity and lack of known active exploits reduce the immediate risk. Organizations relying on JeeSite for critical business functions may face confidentiality breaches if attackers succeed. Since the vulnerability does not affect integrity or availability directly, it is less likely to cause service disruption or data manipulation. The absence of vendor patches means that vulnerable systems remain exposed, increasing long-term risk. Attackers with sufficient expertise could use this flaw as part of a multi-stage attack chain, especially in environments where JeeSite is exposed to the internet. Overall, the impact is moderate but could escalate if combined with other vulnerabilities or misconfigurations.

Summary

CVE-2026-3405 identifies a path traversal vulnerability in thinkgem JeeSite, a Java-based enterprise web application framework, specifically affecting versions 5.15.0 and 5.15.1. The vulnerability resides in an unspecified function within the Connection Handler component, which improperly validates or sanitizes user-supplied input related to file paths. This flaw enables remote attackers to craft malicious requests that traverse directories outside the intended scope, potentially accessing sensitive files on the server. The attack vector requires no authentication or user interaction but is rated as having high complexity, indicating that exploitation demands detailed knowledge of the system and precise conditions. The CVSS 4.0 base score is 2.3, reflecting a low severity primarily due to the difficulty of exploitation and limited impact scope. No public exploits are known to be actively used in the wild, and the vendor has not issued patches or responded to the vulnerability report. The lack of vendor response increases the risk that unpatched systems remain vulnerable. The vulnerability mainly threatens confidentiality by exposing files that should remain protected, but does not directly affect integrity or availability. Given the nature of JeeSite as an enterprise framework, the vulnerability could be leveraged in targeted attacks against organizations using this software for internal or customer-facing applications.

References

Community reviews

Loading reviews…