CVE-2026-109698

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

EUVD-2026-102028 ↗

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.
Kitae Park Mang Board WP <= 2.4.4
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1677Zero's internal tracking ID, independent of the CVE number., permanent identifier
6d 07h 36msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h07m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Mang Board WP mangboard through version 2.4.4 is affected by an SQL injection vulnerability. An attacker may be able to alter database queries; the available evidence does not establish authentication or other preconditions.

mitigation

Update Mang Board WP mangboard when a vendor-fixed release becomes available. Until then, reduce exposure by restricting access to the affected WordPress functionality and monitoring for unexpected database-query activity.

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.29%20th percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 12:09Z
Δ 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-15 12:09Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1677",
  "cve_id": "CVE-2026-109698",
  "display_id": "CVE-2026-109698",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-102028",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Mang Board WP mangboard",
  "summary": "Mang Board WP mangboard through version 2.4.4 is affected by an SQL injection vulnerability. An attacker may be able to alter database queries; the available evidence does not establish authentication or other preconditions.",
  "mitigation": "Update Mang Board WP mangboard when a vendor-fixed release becomes available. Until then, reduce exposure by restricting access to the affected WordPress functionality and monitoring for unexpected database-query activity.",
  "vendor": "Kitae Park",
  "product": "Mang Board WP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.4.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "mangboard",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "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.0029,
  "epss_percentile": 0.2041,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.1481279,
  "t0_at": "2026-10-15T12:09:05.215000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T12:09:05.215000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T12:09:05.215000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109698"
    }
  }
}

published 2026-10-15 12:47Z
last change 2026-10-21 18:49Z

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.