CVE-2026-92536

validatedZero produced an exploit or a check.

GHSA-fc4p-8rjj-4hfw ↗EUVD-2026-91890 ↗

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.
properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress <= 4.17.4
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-410, permanent identifier
+1h21mTTV
53mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+81magent stopped
0
+30min
+60min
+90min

description

ProfilePress for WordPress through version 4.17.4 can expose other users’ email addresses, login names, and registration dates. An attacker needs subscriber-level access in the normal case; unauthenticated exposure is possible when WordPress user registration is enabled.

mitigation

Disable public user registration immediately if it is not required, and restrict or review subscriber accounts. Until a patched ProfilePress release is available, deactivate the plugin or its member-directory functionality where the exposure is unacceptable.

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.
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.63%49th percentile
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 03:25Z
Δ 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 check: a technique exists and was validated, 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-03 03:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-410",
  "cve_id": "CVE-2026-92536",
  "display_id": "CVE-2026-92536",
  "ghsa_id": "GHSA-fc4p-8rjj-4hfw",
  "euvd_id": "EUVD-2026-91890",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Sensitive information exposure in ProfilePress",
  "summary": "ProfilePress for WordPress through version 4.17.4 can expose other users’ email addresses, login names, and registration dates. An attacker needs subscriber-level access in the normal case; unauthenticated exposure is possible when WordPress user registration is enabled.",
  "mitigation": "Disable public user registration immediately if it is not required, and restrict or review subscriber accounts. Until a patched ProfilePress release is available, deactivate the plugin or its member-directory functionality where the exposure is unacceptable.",
  "vendor": "properfraction",
  "product": "Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.17.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress",
      "purl": null
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0063,
  "epss_percentile": 0.4946,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 52.83851046666667,
  "t0_at": "2026-10-03T03:25:43.360000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T04:46:40.526759+00:00",
      "days": 0.056217207858796296,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T03:25:43.360000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T03:25:43.360000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T03:25:43.360000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92536"
    }
  }
}

published 2026-10-03 03:53Z
last change 2026-10-21 04:45Z

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.