Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to xxl-job admin panel (PR:L)
-
DeliveryInject script into job name/author field
-
ExploitPayload stored in Task Management view
-
ExecutionAdmin opens job list, script executes
-
ImpactSteal session / act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account with access to the xxl-job admin Task Management interface (JobInfoController job create/edit) to inject the payload into the 'name' or 'author' argument (PR:L). Exploitation further requires victim user interaction (UI:P/UI:R): a second operator or administrator must load the job list/detail page for the stored script to execute. Limiting factors: the admin console is typically internal/not internet-exposed, self-XSS by the injecting account is meaningless, and impact is confined to integrity of the browser session (no direct server compromise). Applies to xxl-job versions up to 3.4.2/3.5.0. |
| Impact | This is a low-real-risk issue despite being publicly disclosed with PoC. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N) and the vendor's 2.0 score correctly capture a minor stored/reflected XSS in an authenticated admin-only interface: an attacker must already hold valid xxl-job credentials with job-management access (PR:L) AND a second user must view the malicious job entry (UI:P/UI:R). Exploitation status: publicly available exploit code exists (PoC on GitHub, hhhh333/CVE) but there is NO CISA KEV listing and no EPSS score was provided, so there is no evidence of active or widespread exploitation. SSVC-wise this is not automatable and technical impact is partial (integrity-only, VI:L). The main disputable point: VulDB rated confidentiality VC:N, but stored XSS executing in an authenticated admin's browser can realistically enable session/CSRF-token theft, so a modest C:L is defensible - this would raise the real severity slightly above the vendor's 2.0. Bottom line: genuine but low priority; patch on a normal cycle, prioritize behind unauthenticated or higher-impact findings. Note the vendor did not respond to the disclosure, so no official fix version is confirmed. |
| Exploit ScenarioDerived | An authenticated user with access to the xxl-job admin Task Management interface creates or edits a scheduled job, injecting a JavaScript payload into the job 'name' or 'author' field. When another operator or administrator opens the job list/detail view, the script executes in their browser session, enabling session hijacking or actions performed as the victim. A public PoC demonstrating the injection exists on GitHub. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 21, 2026
Stored cross-site scripting in XXL-JOB (xxl-job) 3.4.2 and 3.5.0 lets an authenticated operator inject script through the job 'name' or 'author' fields in the admin Task Management interface (JobInfoController); the payload is persisted and executes in the browser of any other user who later opens the affected job list or detail page. Publicly available exploit code exists, but exploitation requires an existing admin-console account with job create/edit rights plus interaction from a second user, so the practical risk is assessed as low despite the public disclosure. No confirmation of active exploitation (CISA KEV) is present in the available intelligence.
RemediationAI
No vendor-released patch identified at time of analysis: the reporter contacted the XXL-JOB maintainers before public disclosure and received no response, so there is no fixed version to upgrade to and remediation must be compensating. The most effective control is to stop exposing the admin console beyond a trusted boundary - bind xxl-job-admin to an internal interface, place it behind a VPN or zero-trust proxy, and restrict the /jobinfo add and update endpoints to a small set of trusted administrators, accepting that this reduces remote operational convenience. In addition, remove XSS exposure at the application layer by adding strict input validation (reject HTML/markup in 'name' and 'author') and context-aware output encoding in the job list/detail templates and any JSON consumers, or deploy a WAF rule that blocks markup in those POST parameters - noting that template-level fixes must be re-applied after every XXL-JOB upgrade and WAF bypasses are possible. A restrictive Content-Security-Policy without 'unsafe-inline' on the console will neutralise most payload execution but may break existing console scripts and needs testing before rollout. Detailed technical details are available at https://github.com/hhhh333/CVE/blob/main/xxl-job-xss%202.md and https://vuldb.com/vuln/408060.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
XXL-JOB is a distributed Java/Spring Boot task-scheduling platform whose management console (xxl-job-admin) is used to register executors and define cron-like jobs. The affected component is the Task Management Interface implemented by xxl-job-admin/src/main/java/com/xxl/job/admin/business/controller/JobInfoController.java, which handles job creation and editing and accepts user-supplied 'name' and 'author' parameters. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., stored/persistent XSS): the values are stored without proper sanitisation and later rendered into the admin HTML pages and JSON payloads without context-aware output encoding, so injected markup executes in the victim's browser session in the origin of the admin console. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) both confirm the attack is network-reachable, requires low privileges (a valid authenticated console user), and depends on a victim user loading the injected view; scope change and low confidentiality/integrity impact indicate the effect is confined to the victim's browser session rather than the scheduling server itself. The scheduling engine, executors, and job execution plane are not directly compromised by this flaw.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Authenticated job-management access needed (PR:L) and victim must view the entry (UI:R); stored XSS crosses into the victim's browser context (S:C) with limited confidentiality/integrity impact.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability has been found in xuxueli xxl-job up to 3.4.2/3.5.0. This vulnerability affects unknown code of the file xxl-job-admin/src/main/java/com/xxl/job/admin/business/controller/JobInfoController.java of the component Task Management Interface. The manipulation of the argument name/author leads to cross site scripting. It is possible to initiate the attack 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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
EUVD-2026-83844
GHSA-xr2h-v539-xc2h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB