CVE-2026-26719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross Site Scripting vulnerability in xxl-job-admin v.3.0.0 allows a remote attacker to execute arbitrary code via a crafted HTTP GET request containing a malicious script
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross Site Scripting (XSS) vulnerability in xxl-job-admin v3.0.0 allows remote attackers to inject malicious script payloads via crafted HTTP GET request parameters, potentially executing arbitrary JavaScript in victim browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate xxl-job-admin installationSearch for xxl-job-admin web application files, WAR archives, or Docker containers in your environment. Check common deployment directories such as /opt, /var/lib, or application folders. Look for files named 'xxl-job-admin' or 'xxl-job' in your infrastructure.Affected if xxl-job-admin is present in the environment
-
Identify installed versionCheck the version information in the deployed application. This is typically found in the pom.xml file if built from source, a version manifest, or the application startup logs. Look for version markers indicating 3.0.0.Affected if The installed version is exactly 3.0.0
-
Verify web interface exposureConfirm that the xxl-job-admin web interface is network-accessible. Check your firewall rules, reverse proxy configurations, or service bindings to determine if HTTP/HTTPS endpoints are exposed to users or networks where attackers could send crafted requests.Affected if The admin interface is externally accessible without proper network segmentation
-
Test for parameter reflectionSend a test HTTP GET request to the xxl-job-admin endpoints with a benign script payload in query parameters (for example, ?callback=<script>alert(1)</script>). Capture the response and examine if the parameter value is reflected unchanged in the HTML output.Affected if User-supplied parameters are reflected in responses without encoding or validation
You are affected if xxl-job-admin version 3.0.0 is running and its web interface is accessible to send HTTP GET requests with unsanitized parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and context-appropriate output encoding on all user-supplied parameters in HTTP requests; audit and patch all vulnerable endpoints.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data