CVE.org (no NVD analysis yet)· CNA WPScan

CVE-2026-75823: WP User Frontend 3.5.29 - 4.3.11 - Unauthenticated Privilege Escalation via Registration Role Encryption

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Unknown User Frontend 4.3.12.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Unknown User Frontend 4.3.12 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The User Frontend WordPress plugin before 4.3.12 does not prevent tampering with the role assigned by its registration form, allowing unauthenticated users to register with a higher privileged role, such as Editor. This affects installations running a PHP build where the sodium extension is unavailable, and where a registration page has been configured. The administrator role cannot be obtained this way.

HighCVSS 7.4 · v3.1—No exploit Fix available

Pre-auth

EUVD-2026-89639

Published: Sep 30, 2026
Updated: Sep 30, 2026
EPSS: 0.2% · 16th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Is User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown User Frontend
- 3.5.29 and later · before 4.3.12affected · semver

Same product

unknown: all records

Other highest-scoring records for the same primary product.

CVE-2026-19116WP User Frontend < 4.3.11 - Subscriber+ PHP Object Injection via Frontend Post Edit Form
35Monitor
CVE-2026-14558WP User Frontend < 4.3.10 - Editor+ PHP Object Injection via AI Form Builder
28Monitor
CVE-2026-75824WP User Frontend 2.5.8 - 4.3.11 - Unauthenticated Account Creation with Registration Disabled
21Monitor

Published before and after this one in the same product

← EarlierCVE-2026-14567Aug 28, 2026 · WP User Frontend < 4.3.10 - Unauthenticated User Email and Phone Disclosure via User Directory
21Monitor
← EarlierCVE-2026-17563Sep 2, 2026 · WP User Frontend < 4.3.11 - Unauthenticated Post Creation via Subscription-Gated Form
21Monitor
Later →CVE-2026-115277Oct 30, 2026 · WP User Frontend < 4.3.14 - Reflected XSS via 'field_attr' Parameter
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Unknown User Frontend	4.3.12	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedSep 30, 2026
Fix recordedSep 30, 2026same day
TodayOct 30, 2026+30 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Murad Akhmedovfinder
WPScancoordinator

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1220 · Sep 30, 2026(WordPress Eklenti Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

CVSS— → 7.4Sep 30, 2026, 3:07 PM UTC
Severity— → highSep 30, 2026, 3:07 PM UTC
SSVC exploitation— → noneSep 30, 2026, 3:07 PM UTC
Exploit maturity— → noneSep 30, 2026, 7:07 AM UTC
Fix✗ → ✓Sep 30, 2026, 7:07 AM UTC

For records you follow, these changes also arrive as notifications. →

References

wpscan.com/vulnerability/4a385690-3471-4604-aa2a-e120bb31ca53/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records