VulnerabilityPublished 28 Apr 2026

CVE-2026-7303: Xuxueli xxl-job · Improper Control of Resource Identifiers

Affects Xuxueli xxl-jobSource CVE Database V5

Compare

Public exploit available · CVSS 6.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.3Medium

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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: None
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: 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: 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 28 Apr 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
Xuxuelixxl-job	Affected =3.3.0 =3.3.1 =3.3.2	Fixed in–
Mavencom.xuxueli/xxl-job`pkg:maven/com.xuxueli/xxl-job`Other threats	Affected =3.3.0 =3.3.1 =3.3.2	Fixed in–

CPE configurations (1)

cpe:2.3:a:xuxueli:xxl-job:*:*:*:*:*:*:*:*

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

AI-suggested

Upgrade the affected Xuxueli xxl-job component to version 3.4.0 or later, which contains the official fix for this vulnerability (commit d24e4ccd6073cc75305e1d3b9c29bc8db7437e7a). Patch status is confirmed by the vendor recommendation. No other mitigation steps are specified.

Description

CVE-2026-7303 is a medium severity vulnerability in Xuxueli xxl-job versions up to 3.3.2. It involves improper control of resource identifiers in the logDetailCat function of the Execution Log Handler component. The vulnerability arises from manipulation of the logId argument, which can be exploited remotely but requires high complexity and no user interaction. An exploit has been publicly released. Upgrading to version 3.4.0 addresses this issue.

Impact

The vulnerability allows remote attackers to manipulate resource identifiers via the logId parameter in the execution log handler, which may lead to unauthorized access or information disclosure related to job execution logs. The exploitability is difficult due to high complexity, and no privileges or user interaction are required. Although an exploit is publicly available, there are no confirmed reports of exploitation in the wild.

Summary

This vulnerability affects the logDetailCat function in the JobLogController.java file of Xuxueli xxl-job up to version 3.3.2. Improper control of the logId parameter allows an attacker to manipulate resource identifiers, potentially leading to unauthorized access or other impacts related to execution log handling. The attack vector is network-based with high attack complexity and no privileges or user interaction required. The vulnerability has a CVSS 4.0 base score of 6.3 (medium severity). A patch is available in version 3.4.0, identified by commit d24e4ccd6073cc75305e1d3b9c29bc8db7437e7a.

References

Community reviews

Loading reviews…