CVE-2026-120070

validatedZero produced an exploit or a check.

GHSA-558h-x4v5-3hwr ↗EUVD-2026-114657 ↗

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.
wedevs User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission <= 4.3.13
ETK-2026-3171Zero's internal tracking ID, independent of the CVE number., permanent identifier
+3h17mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+3h17magent stopped
0
+1h
+2h
+3h

description

User Frontend for WordPress versions through 4.3.13 can allow a logged-in Subscriber or higher-privileged user to bypass restrictions on submitted post content. An attacker may cause an Editor-level registration path to be exposed publicly and create a privileged account. Automatic login after registration enables immediate use of the newly created account.

mitigation

Disable frontend post submission for untrusted, low-privilege users or deactivate the plugin until a corrected release is confirmed. Disable automatic login after registration, and review published content and accounts for unauthorized registration forms or elevated users.

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.
yes, low privileges
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 07:46Z
Δ 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.

this entry in the feed

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

{
  "etk_id": "ETK-2026-3171",
  "cve_id": "CVE-2026-120070",
  "display_id": "CVE-2026-120070",
  "ghsa_id": "GHSA-558h-x4v5-3hwr",
  "euvd_id": "EUVD-2026-114657",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Privilege escalation in User Frontend WordPress plugin",
  "summary": "User Frontend for WordPress versions through 4.3.13 can allow a logged-in Subscriber or higher-privileged user to bypass restrictions on submitted post content. An attacker may cause an Editor-level registration path to be exposed publicly and create a privileged account. Automatic login after registration enables immediate use of the newly created account.",
  "mitigation": "Disable frontend post submission for untrusted, low-privilege users or deactivate the plugin until a corrected release is confirmed. Disable automatic login after registration, and review published content and accounts for unauthorized registration forms or elevated users.",
  "vendor": "wedevs",
  "product": "User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.3.13"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission",
      "purl": null
    }
  ],
  "cwes": null,
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.009105216666666667,
  "t0_at": "2026-10-31T07:46:53.190000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-31T11:04:20.353349+00:00",
      "days": 0.1371199461689815,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T07:46:53.190000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-31T07:46:53.190000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T07:46:53.190000+00:00",
      "url": "https://github.com/advisories/GHSA-558h-x4v5-3hwr"
    }
  }
}

published 2026-10-31 11:04Z
last change 2026-10-31 15:49Z

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.