CVE-2025-7787VulnerabilityPublished 18 Jul 2025

CVE-2025-7787: Xuxueli xxl-job · Server-Side Request Forgery

Affects Xuxueli xxl-jobSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% 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: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: Low
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: 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: 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 18 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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
Mavencom.xuxueli/xxl-job`pkg:maven/com.xuxueli/xxl-job`Other threats	Affected =3.1.0 =3.1.1	Fixed in–

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

AI-suggested

1. Immediate mitigation should include restricting network access from the xxl-job server to only trusted and necessary internal resources using firewall rules or network segmentation to limit SSRF impact. 2. Implement strict input validation and sanitization on any parameters processed by the httpJobHandler function to prevent injection of malicious URLs. 3. Monitor logs for unusual outbound HTTP requests originating from the xxl-job server to detect potential exploitation attempts. 4. If possible, disable or restrict the use of the vulnerable httpJobHandler functionality until a patch is available. 5. Employ web application firewalls (WAFs) with SSRF detection capabilities to block suspicious requests targeting the vulnerable endpoint. 6. Stay updated with vendor advisories and apply official patches promptly once released. 7. Conduct internal security assessments to identify any exposure of internal services that could be targeted via SSRF and harden those services accordingly.

Description

A vulnerability, which was classified as critical, was found in Xuxueli xxl-job up to 3.1.1. Affected is the function httpJobHandler of the file src\main\java\com\xxl\job\executor\service\jobhandler\SampleXxlJob.java. The manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the xxl-job scheduling framework, this SSRF vulnerability poses a risk of unauthorized internal network reconnaissance and potential access to sensitive internal services. Given that xxl-job is used to automate and schedule critical business processes, exploitation could lead to disruption of scheduled tasks or unauthorized access to internal APIs and resources. The impact on confidentiality is moderate, as SSRF can expose internal endpoints and data. Integrity and availability impacts are lower but possible if the attacker leverages SSRF to trigger further attacks or denial of service conditions. Organizations in sectors with high reliance on internal network segmentation and automation, such as finance, manufacturing, and critical infrastructure, could face increased risk. The medium CVSS score reflects that while the vulnerability is exploitable remotely, it requires some level of privilege, limiting the scope of attackers. However, the public disclosure and lack of patches increase urgency for mitigation to prevent exploitation attempts.

Summary

CVE-2025-7787 is a server-side request forgery (SSRF) vulnerability found in the Xuxueli xxl-job open-source distributed task scheduling framework, specifically affecting versions 3.1.0 and 3.1.1. The vulnerability exists in the httpJobHandler function within the SampleXxlJob.java source file. SSRF vulnerabilities allow an attacker to induce the server-side application to make HTTP requests to arbitrary domains or IP addresses, potentially bypassing firewall restrictions and accessing internal resources that are not otherwise exposed externally. In this case, the vulnerability can be exploited remotely without authentication or user interaction, as indicated by the CVSS vector. The CVSS 4.0 base score is 5.3, categorized as medium severity, reflecting limited impact on confidentiality, integrity, and availability, and requiring low privileges (PR:L) but no user interaction. The vulnerability does not require authentication but does require low privileges, which suggests that an attacker with some level of access to the system or network could exploit it. The SSRF could be leveraged to scan internal networks, access sensitive internal services, or perform further attacks such as data exfiltration or lateral movement. Although no known exploits are currently reported in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The lack of available patches at the time of publication means that affected users must rely on mitigation strategies until an official fix is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Jul 2025, 14:46 UTC

Technical details

References

Community reviews

Related threats