WordPress WP User Frontend plugin <= 4.3.11 - Bypass Vulnerability vulnerability

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps weDevs/WP User Frontend (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for weDevs/WP User Frontend.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 23, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• Jawn: Uncontrolled nesting depth in JSON parserSame generic ecosystem
• Wire Swift runtime: negative LENGTH_DELIMITED length in skipGroup() crashes any protobuf-decoding serviceSame generic ecosystem
• Jawn: Quadratic parsing effort in AsyncParserSame generic ecosystem
• Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentialsSame generic ecosystem
• Formie: Unauthenticated users can overwrite incomplete submissions via submit actionSame generic ecosystem
• Formie: Missing authorization on sent notification resend modal exposes submission PIISame generic ecosystem