CVE-2026-132620

validatingZero is analyzing and reversing it now.

GHSA-g62x-87gv-5qwj ↗EUVD-2026-132028 ↗

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.
quantumcloud WPBot – AI ChatBot for WordPress & Growth Suite: SEO, AI Writer, Email Marketing, Social Media <= 9.1
ETK-2026-5123Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

WPBot for WordPress is affected by stored cross-site scripting in releases through 9.1. An unauthenticated attacker may cause script to be stored through chat input, which can execute in an administrator's browser when they view Chat Sessions.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Disable the WPBot plugin until a vendor release confirmed to correct this issue can be installed. Limit administrator access to the Chat Sessions screen and avoid opening untrusted chat records.

check
building now
exploit
not yet
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.
–
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
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-21 07:45Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-21 07:45Z
    ghsa: trigger signal, started the run
  2. 2026-11-21 07:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-5123",
  "cve_id": "CVE-2026-132620",
  "display_id": "CVE-2026-132620",
  "ghsa_id": "GHSA-g62x-87gv-5qwj",
  "euvd_id": "EUVD-2026-132028",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in WPBot WordPress plugin",
  "summary": "WPBot for WordPress is affected by stored cross-site scripting in releases through 9.1. An unauthenticated attacker may cause script to be stored through chat input, which can execute in an administrator's browser when they view Chat Sessions.",
  "mitigation": "Disable the WPBot plugin until a vendor release confirmed to correct this issue can be installed. Limit administrator access to the Chat Sessions screen and avoid opening untrusted chat records.",
  "vendor": "quantumcloud",
  "product": "WPBot – AI ChatBot for WordPress & Growth Suite: SEO, AI Writer, Email Marketing, Social Media",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 9.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WPBot – AI ChatBot for WordPress & Growth Suite: SEO, AI Writer, Email Marketing, Social Media",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-21T07:45:19.605000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-21T07:45:19.605000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-21T07:45:19.605000+00:00",
      "url": "https://github.com/advisories/GHSA-g62x-87gv-5qwj"
    }
  }
}

published 2026-11-21 10:25Z
last change 2026-11-21 10:52Z

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.