Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106707 Overview
CVE-2026-106707 is a stored Cross-Site Scripting (XSS) vulnerability [CWE-79] in XXL-JOB, an open-source distributed task scheduling platform. The flaw affects versions <=3.5.0-SNAPSHOT and resides in the job log list page (/joblog). An authenticated user with permission on a target executor job group can inject arbitrary JavaScript through the executorParam argument of the manual-trigger endpoint POST /jobinfo/trigger. The injected payload executes in the browser of any administrator or operator who later views the affected job log entry, enabling session theft, forced actions, and privilege abuse within the scheduler console.
Critical Impact
Authenticated attackers can persist JavaScript in job logs that executes against higher-privileged users browsing the XXL-JOB admin console.
Affected Products
- XXL-JOB versions <=3.5.0-SNAPSHOT
- XXL-JOB admin console /joblog page
- XXL-JOB manual trigger endpoint POST /jobinfo/trigger
Discovery Timeline
- 2026-10-15 - CVE-2026-106707 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-106707
Vulnerability Analysis
XXL-JOB exposes a manual-trigger endpoint that accepts a user-supplied executorParam value. This value is stored and later rendered on the job log list page without proper output encoding or input sanitization. When an operator loads /joblog to review historical executions, the browser parses the stored payload as HTML and executes any attacker-controlled JavaScript.
Because the payload persists in the scheduler's log store, exploitation does not require social engineering a specific URL. Any user with access to the affected job group's logs becomes a target. The scope change reflects that script execution crosses from the lower-privileged triggering account into the browsing context of higher-privileged administrators.
Root Cause
The root cause is missing contextual output encoding when rendering stored job parameters in the admin UI. The executorParam field is treated as display-safe text at render time, but the application never neutralizes HTML metacharacters or script tags before writing the value into the DOM. This is a classic server-side-persisted, client-side-executed XSS pattern tracked under [CWE-79].
Attack Vector
Exploitation requires an authenticated session with permission on at least one executor job group. The attacker issues a POST /jobinfo/trigger request against a job they can control and sets executorParam to an HTML or JavaScript payload. The scheduler accepts the request, records the trigger in the job log, and renders the stored parameter when an administrator opens the /joblog page. The payload then runs with the privileges of the viewing user, allowing it to read session cookies, call privileged admin APIs, or modify scheduler configuration.
See the GitHub CVE-2026-106707 Report and the XXL-JOB project repository for additional technical context.
Detection Methods for CVE-2026-106707
Indicators of Compromise
- Entries in the XXL-JOB job log where the executorParam field contains HTML tags, <script> blocks, event handlers such as onerror=, or javascript: URIs.
- Unexpected POST /jobinfo/trigger requests originating from low-privileged accounts targeting job groups they rarely use.
- Admin console sessions issuing privileged API calls immediately after an operator opened /joblog.
Detection Strategies
- Inspect application and reverse-proxy access logs for POST /jobinfo/trigger bodies containing angle brackets, quotes, or script keywords in the executorParam parameter.
- Deploy a web application firewall rule that flags XSS metacharacters in request bodies sent to XXL-JOB admin endpoints.
- Review stored job log records for persisted markup and quarantine entries that fail an HTML-safe-content check.
Monitoring Recommendations
- Alert on anomalous outbound requests from browsers of XXL-JOB administrators, which may indicate token exfiltration via injected script.
- Monitor XXL-JOB admin accounts for sudden configuration changes, new executors, or privilege grants that follow log-page views.
- Correlate authentication telemetry with job-trigger activity to surface accounts abusing low-tier permissions to plant payloads.
How to Mitigate CVE-2026-106707
Immediate Actions Required
- Restrict access to the XXL-JOB admin console to trusted operators and place it behind an authenticated reverse proxy or VPN.
- Audit all existing job log entries and purge records whose executorParam field contains HTML or script content.
- Revoke executor job group permissions from accounts that do not require manual trigger capability.
Patch Information
No vendor patch is referenced in the NVD entry at the time of publication. Track the XXL-JOB project repository for releases beyond 3.5.0-SNAPSHOT that address the stored XSS in the job log view, and apply the fix as soon as it is available.
Workarounds
- Enforce server-side validation that rejects executorParam values containing <, >, or quote characters until a patched release is deployed.
- Add a reverse-proxy rule that strips or blocks HTML metacharacters in the body of POST /jobinfo/trigger requests.
- Configure a strict Content Security Policy on the XXL-JOB admin console to block inline script execution and untrusted script sources.
# Example NGINX rule to block HTML metacharacters in executorParam
location /jobinfo/trigger {
if ($request_body ~* "executorParam=[^&]*(<|%3C|script|onerror|javascript:)") {
return 403;
}
proxy_pass http://xxl_job_admin;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

