CVE-2026-111399

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

GHSA-qx9c-xg53-v6j6 ↗EUVD-2026-102859 ↗

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.
PT Norther Lights Production MapSVG <= 8.16.1
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1821Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 06h 00msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+11h15m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

MapSVG versions through 8.16.1 are affected by an SQL injection flaw. A user with low-level access may be able to manipulate database queries through the plugin.

mitigation

Upgrade from version 8.16.1 or earlier to a later vendor release after confirming it addresses this issue. Restrict low-privilege accounts' access to MapSVG and remove the plugin where it is not needed.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.26%16th percentile
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 12:30Z
Δ 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-16 12:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1821",
  "cve_id": "CVE-2026-111399",
  "display_id": "CVE-2026-111399",
  "ghsa_id": "GHSA-qx9c-xg53-v6j6",
  "euvd_id": "EUVD-2026-102859",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in MapSVG WordPress plugin",
  "summary": "MapSVG versions through 8.16.1 are affected by an SQL injection flaw. A user with low-level access may be able to manipulate database queries through the plugin.",
  "mitigation": "Upgrade from version 8.16.1 or earlier to a later vendor release after confirming it addresses this issue. Restrict low-privilege accounts' access to MapSVG and remove the plugin where it is not needed.",
  "vendor": "PT Norther Lights Production",
  "product": "MapSVG",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 8.16.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "mapsvg-lite-interactive-vector-maps",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": 0.0026,
  "epss_percentile": 0.1668,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.628100266666667,
  "t0_at": "2026-10-16T12:30:32.747000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T12:30:32.747000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T12:30:32.747000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111399"
    }
  }
}

published 2026-10-16 23:14Z
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.