← back to feed
CVE-2026-116520

CVE-2026-116520

validatedZero produced an exploit or a check.

GHSA-7x9h-cjm5-x9fc ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
buildwps PPWP – Password Protect Pages <= 1.9.26
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-3147Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.2cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
+27mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+27magent stopped
0
+5min
+10min
+15min
+20min
+25min

description

PPWP – Password Protect Pages versions through 1.9.26 are affected by stored cross-site scripting. An unauthenticated attacker may cause script content to run in a visitor's browser when they view an affected page, if comment handling allows the content to be accepted and later displayed. The documented path relies on WordPress comment processing and automatic approval of comments associated with a previously approved identity.

mitigation

Disable or restrict comments on pages using the plugin and turn off automatic approval for previously approved commenters. Review and remove untrusted comments or shortcode content, and monitor the plugin publisher for an updated release.

check
available
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.
deterministic
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
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 05:33Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-31 05:33Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-116520
  2. 2026-10-31 05:59Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3147",
  "cve_id": "CVE-2026-116520",
  "display_id": "CVE-2026-116520",
  "ghsa_id": "GHSA-7x9h-cjm5-x9fc",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in PPWP – Password Protect Pages",
  "summary": "PPWP – Password Protect Pages versions through 1.9.26 are affected by stored cross-site scripting. An unauthenticated attacker may cause script content to run in a visitor's browser when they view an affected page, if comment handling allows the content to be accepted and later displayed. The documented path relies on WordPress comment processing and automatic approval of comments associated with a previously approved identity.",
  "mitigation": "Disable or restrict comments on pages using the plugin and turn off automatic approval for previously approved commenters. Review and remove untrusted comments or shortcode content, and monitor the plugin publisher for an updated release.",
  "vendor": "buildwps",
  "product": "PPWP – Password Protect Pages",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.9.26"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "PPWP – Password Protect Pages",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "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": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.00957915,
  "t0_at": "2026-10-31T05:33:08.490000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-31T05:59:46.448108+00:00",
      "days": 0.01849488550925926,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T05:33:08.490000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-31T05:33:08.490000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T05:33:08.490000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116520"
    }
  }
}

published 2026-10-31 05:59Z
last change 2026-10-31 07: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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.