Skip to content

← Public intelligence

Maven package

com.xuxueli:xxl-job-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7MavenPublished

    Improper Preservation of Permissions in xxl-job

    CVE-2024-42681 · GHSA-cpfp-m5qw-c4r3

    Affected
    • Maven com.xuxueli:xxl-job-core <= 2.4.1
    Fixed in
    2.4.2· Vendor fix available
    Issue
    Insecure Permissions vulnerability in xxl-job v.2.4.1 allows a remote attacker to execute arbitrary code via the Sub-Task ID component.

    Recommended action: Upgrade to 2.4.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.8MavenPublished

    XXL-JOB vulnerable to Server-Side Request Forgery (SSRF)

    CVE-2022-43183 · GHSA-83w4-x5w9-hf4h

    Affected
    • Maven com.xuxueli:xxl-job-core < 2.4.0
    Fixed in
    2.4.0· Vendor fix available
    Issue
    XXL-Job before v2.4.0 contains a Server-Side Request Forgery (SSRF) via the component /admin/controller/JobLogController.java.

    Recommended action: Upgrade to 2.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.1MavenPublished

    Cross-site Scripting in XXL-JOB

    CVE-2020-29204 · GHSA-wc73-w5r9-x9pc

    Affected
    • Maven com.xuxueli:xxl-job-core < 2.3.0
    Fixed in
    2.3.0· Vendor fix available
    Issue
    XXL-JOB 2.2.0 allows Stored XSS (in Add User) to bypass the 20-character limit via xxl-job-admin/src/main/java/com/xxl/job/admin/controller/UserController.java.

    Recommended action: Upgrade to 2.3.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →