dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-3733

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was detected in xuxueli xxl-job up to 3.3.2. This impacts an unknown function of the file source-code/src/main/java/com/xxl/job/admin/controller/JobInfoController.java. The manipulation results in server-side request forgery. It is possible to launch the attack remotely. The exploit is now public and may be used. The project maintainer closed the issue report with the following statement: "Access token security verification is required." (translated from Chinese)

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 confidence

A server-side request forgery (SSRF) vulnerability exists in xxl-job's JobInfoController.java up to version 3.3.2 due to missing or inadequate access token validation. This allows remote attackers to trick the server into making arbitrary HTTP requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or internal network infrastructure.

MitigationImplement proper access token security verification on the affected JobInfoController endpoints to ensure all requests are authenticated before processing, following the maintainer's guidance. Restrict outbound network connections from the application server as a defense-in-depth measure.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify xxl-job installation and version
    Locate the xxl-job web application JAR or WAR file, or check the build/deployment artifacts. Examine the manifest file or version file (often in META-INF/MANIFEST.MF or version.properties) to determine the installed version.
    Affected if The installed version is 3.3.2 or any earlier version (e.g., 3.0.0 through 3.3.2).
  2. Locate the JobInfoController component
    Inspect the deployed application WAR/JAR for the class file com.xxl.job.admin.controller.JobInfoController.class or its source code equivalent.
    Affected if JobInfoController.java exists in the deployment and the version is 3.3.2 or earlier.
  3. Verify access token configuration
    Examine the application configuration files (application.properties or application.yml) for the access token settings. Look for properties like xxl.job.accessToken or similar token-related configuration under the xxl-job admin settings.
    Affected if The access token is missing, blank, set to a weak/default value, or not enforced on the JobInfoController endpoints.
  4. Test endpoint accessibility
    Attempt to access the JobInfo REST endpoints (typically /jobinfo or /api/jobinfo paths) without providing valid authentication credentials. Use a tool like curl to send requests to internal endpoints such as http://localhost:8080/ or cloud metadata endpoints like http://169.254.169.254/.
    Affected if The endpoints process requests and return valid responses without requiring proper access token validation.
  5. Check network exposure
    Review firewall rules, networkACLs, or reverse proxy configurations to determine if the xxl-job admin console is exposed to untrusted networks or the public internet.
    Affected if The JobInfoController endpoints are reachable from untrusted networks without authentication barriers.

A user is affected if xxl-job version 3.3.2 or earlier is deployed and the JobInfoController endpoints lack proper access token enforcement, allowing unauthenticated SSRF requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper access token security verification on the affected JobInfoController endpoints to ensure all requests are authenticated before processing, following the maintainer's guidance. Restrict outbound network connections from the application server as a defense-in-depth measure.

Recommended fix Moderate confidence

xxl-job version 3.3.3 or later

  1. 1. Backup your current xxl-job installation and database
  2. 2. Identify your current xxl-job version by checking the version in pom.xml or the runtime version display
  3. 3. Upgrade xxl-job to version 3.3.3 or later, as version 3.3.2 and earlier are affected by this SSRF vulnerability
  4. 4. If using a custom build, ensure the fix from the upstream repository is applied: the JobInfoController now properly validates access tokens before processing requests
  5. 5. After upgrade, verify that the /jobinfo or related API endpoints require valid access token authentication
  6. 6. Test that the SSRF vulnerability is no longer exploitable by attempting to make the server request arbitrary URLs without proper authentication
Caveat Review release notes for any API changes between 3.3.2 and the target version; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3733 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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