CVE-2026-96327

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7wf8-p84v-8jfr ↗EUVD-2026-95598 ↗

no check availablenot proven exploitable
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.
vibethemes WPLMS < 1.9.9.8.2
fixed in 1.9.9.8.2
ETK-2026-1076Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 14h 00msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h47m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

WPLMS plugin versions before 1.9.9.8.2 are affected by a blind SQL injection flaw. An attacker able to reach a vulnerable installation may influence database queries and infer information from their results; no specific endpoint or additional configuration prerequisite is provided.

mitigation

Upgrade WPLMS to version 1.9.9.8.2 or later. Until upgraded, restrict access to the affected installation to trusted users and networks where feasible.

fixed in 1.9.9.8.2

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 10:00Z
Δ 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: an exploit technique exists, 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-09 10:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-09 10:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1076",
  "cve_id": "CVE-2026-96327",
  "display_id": "CVE-2026-96327",
  "ghsa_id": "GHSA-7wf8-p84v-8jfr",
  "euvd_id": "EUVD-2026-95598",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Blind SQL injection in WPLMS plugin",
  "summary": "WPLMS plugin versions before 1.9.9.8.2 are affected by a blind SQL injection flaw. An attacker able to reach a vulnerable installation may influence database queries and infer information from their results; no specific endpoint or additional configuration prerequisite is provided.",
  "mitigation": "Upgrade WPLMS to version 1.9.9.8.2 or later. Until upgraded, restrict access to the affected installation to trusted users and networks where feasible.",
  "vendor": "vibethemes",
  "product": "WPLMS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.9.9.8.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.9.9.8.2"
      ],
      "package_name": "wplms_plugin",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": 0.0025,
  "epss_percentile": 0.1532,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.171315483333334,
  "t0_at": "2026-10-09T10:00:18.114000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T10:00:18.114000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T10:00:18.114000+00:00",
      "url": "https://github.com/advisories/GHSA-7wf8-p84v-8jfr"
    }
  }
}

published 2026-10-09 14:30Z
last change 2026-10-21 04:45Z

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.