CVE-2026-107791

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

GHSA-p3pc-rx4j-4w3p ↗EUVD-2026-97244 ↗

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.
WP Comment Cleaner >= 6.1, < 7.2
fixed in 7.2
ETK-2026-2199Zero's internal tracking ID, independent of the CVE number., permanent identifier
16h 25msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+203h57m
0
+2h
+4h
+6h
+8h
+10h

description

WP Comment Cleaner versions before 7.2 expose a bulk comment-deletion function without sufficient permission and request validation. An authenticated user with minimal site privileges may be able to permanently remove all comments.

mitigation

Upgrade WP Comment Cleaner to version 7.2 or later. Until upgraded, restrict untrusted user accounts and review comment deletion activity.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2199",
  "cve_id": "CVE-2026-107791",
  "display_id": "CVE-2026-107791",
  "ghsa_id": "GHSA-p3pc-rx4j-4w3p",
  "euvd_id": "EUVD-2026-97244",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in WP Comment Cleaner bulk comment deletion",
  "summary": "WP Comment Cleaner versions before 7.2 expose a bulk comment-deletion function without sufficient permission and request validation. An authenticated user with minimal site privileges may be able to permanently remove all comments.",
  "mitigation": "Upgrade WP Comment Cleaner to version 7.2 or later. Until upgraded, restrict untrusted user accounts and review comment deletion activity.",
  "vendor": null,
  "product": "WP Comment Cleaner",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.1, < 7.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.2"
      ],
      "package_name": "WP Comment Cleaner",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 6.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.0697,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.89854911666667,
  "t0_at": "2026-10-12T06:00:08.827000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T06:00:08.827000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T06:00:08.827000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107791"
    }
  }
}

published 2026-10-20 17:34Z
last change 2026-10-21 09:43Z

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.