CVE-2026-26718
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability exists in the xxl-job-admin web application v.3.0.0 that allows an attacker to perform unauthorized modifications to Glue IDE shell scripts. The affected endpoint lacks proper CSRF token validation and accepts arbitrary HTTP methods via a permissive request mapping
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 · high confidenceA CSRF vulnerability in xxl-job-admin v3.0.0 allows attackers to make unauthorized modifications to Glue IDE shell scripts. The affected endpoint lacks CSRF token validation and accepts arbitrary HTTP methods due to a permissive request mapping, enabling malicious cross-site requests that appear legitimate to the application.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify xxl-job-admin versionLocate the deployed xxl-job-admin application and check its version file (such as pom.xml, build.gradle, or version manifest in the WAR/jar package). Compare the version to v3.0.0.Affected if The installed version is exactly v3.0.0 or falls within the v3.0.0 release line.
-
Verify Glue IDE is accessibleAccess the xxl-job web console and navigate to the Glue IDE feature (typically found under a 'Glue' or 'Script' menu option). Confirm the interface loads and allows viewing/editing of job scripts.Affected if The Glue IDE interface is accessible without additional configuration restrictions.
-
Inspect CSRF protection configurationExamine the web application security configuration files (such as Spring Security configuration or WebSecurityConfig) for CSRF token validation settings on endpoints handling Glue IDE script modifications.Affected if CSRF protection is disabled or the Glue IDE endpoint explicitly bypasses CSRF validation.
-
Check HTTP method restrictions on Glue endpointReview the controller mapping annotations (such as @RequestMapping or @PostMapping) for the Glue IDE script modification endpoint in the source code. Determine if the endpoint accepts methods beyond POST (e.g., GET, PUT).Affected if The endpoint mapping allows arbitrary HTTP methods rather than being restricted to POST only.
A user is affected if they are running xxl-job-admin v3.0.0 with the Glue IDE feature accessible and the script modification endpoint lacks CSRF protection or permits non-POST HTTP methods.
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 CSRF token validation on the affected Glue IDE endpoint and restrict the request mapping to accept only necessary HTTP methods (e.g., POST) with proper token verification.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26718 — 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-26718 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