CVE-2026-93855

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

EUVD-2026-112587 ↗

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.
brewlabs SendPress Newsletters <= 1.26.1.20
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-2936Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 18msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h42m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

SendPress Newsletters for WordPress is affected by an SQL injection issue in versions through 1.26.1.20. An unauthenticated remote attacker may be able to access sensitive database information when the public subscriber-management form is exposed.

mitigation

Disable the plugin or remove public access to its subscriber-management form until a patched release is available. Monitor for and install the vendor's update when a fixed version is published.

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.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 03:39Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-29 03:39Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2936",
  "cve_id": "CVE-2026-93855",
  "display_id": "CVE-2026-93855",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-112587",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in SendPress Newsletters",
  "summary": "SendPress Newsletters for WordPress is affected by an SQL injection issue in versions through 1.26.1.20. An unauthenticated remote attacker may be able to access sensitive database information when the public subscriber-management form is exposed.",
  "mitigation": "Disable the plugin or remove public access to its subscriber-management form until a patched release is available. Monitor for and install the vendor's update when a fixed version is published.",
  "vendor": "brewlabs",
  "product": "SendPress Newsletters",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.26.1.20"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SendPress Newsletters",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.7946546,
  "t0_at": "2026-10-29T03:39:14.346000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T03:39:14.346000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T03:39:14.346000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-93855"
    }
  }
}

published 2026-10-29 04:02Z
last change 2026-10-29 06:00Z

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.