← back to feed
CVE-2026-89310

CVE-2026-89310

validatedZero produced an exploit or a check.

EUVD-2026-100874 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
JTL SW GmbH JTL-WMS < 2.0.7; < 2.1.3; < 2.2.1; 1.7.*; 1.8.*; 1.9.*; 1.10.*; 1.11.*
fixed in 2.0.7, 2.1.3, 2.2.1
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1549Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.4cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
+2h31mTTV
38mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+2h31magent stopped
0
+1h
+2h

description

JTL-WMS is affected by an SQL injection flaw in handling a parameter from a request body. An attacker who can submit requests to the affected functionality may execute SQL statements using the application's database account.

mitigation

Upgrade JTL-WMS to version 2.0.7, 2.1.3, or 2.2.1, as appropriate for the deployed release line. Restrict access to the affected application interface until the update is installed.

fixed in 2.0.7, 2.1.3, 2.2.1

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.47%39th percentile
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 06:50Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 06:50Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-89310

this entry in the feed

GET /api/v1/feed/CVE-2026-89310

{
  "etk_id": "ETK-2026-1549",
  "cve_id": "CVE-2026-89310",
  "display_id": "CVE-2026-89310",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-100874",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in JTL-WMS",
  "summary": "JTL-WMS is affected by an SQL injection flaw in handling a parameter from a request body. An attacker who can submit requests to the affected functionality may execute SQL statements using the application's database account.",
  "mitigation": "Upgrade JTL-WMS to version 2.0.7, 2.1.3, or 2.2.1, as appropriate for the deployed release line. Restrict access to the affected application interface until the update is installed.",
  "vendor": "JTL SW GmbH",
  "product": "JTL-WMS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.0.7",
        ">= 0, < 2.1.3",
        ">= 0, < 2.2.1",
        "1.7.*",
        "1.8.*",
        "1.9.*",
        "1.10.*",
        "1.11.*"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.7",
        "2.1.3",
        "2.2.1"
      ],
      "package_name": "JTL-WMS",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
  "epss_score": 0.0047,
  "epss_percentile": 0.3916,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 38.2696791,
  "t0_at": "2026-10-14T06:50:34.005000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-14T09:21:27.865630+00:00",
      "days": 0.10479005358796296,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T06:50:34.005000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-14T06:50:34.005000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T06:50:34.005000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-89310"
    }
  }
}

published 2026-10-14 07:07Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.