Skip to main content

Choose User Role CVE-2026-85128

| EUVDEUVD-2026-81336 HIGH
Improper Privilege Management (CWE-269)
2026-09-17 WPScan GHSA-865c-5jwm-r2qv
7.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Find site with open registration + role selection
  2. Delivery
    Submit registration forging administrator role
  3. Exploit
    Admin approves pending request
  4. Execution
    Account granted admin privileges
  5. Impact
    Full site takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires BOTH of the plugin's non-default features to be enabled simultaneously: the 'role selection at registration' feature must be active, AND public/open account registration must be turned on. The plugin fails to validate the role a registrant requests against the roles the administrator actually chose to offer, so an attacker can request 'administrator'. Critically, the escalated privilege is only granted after an administrator approves the pending registration request (reflected in CVSS UI:R) - an admin who reviews and rejects a suspicious role request blocks the attack entirely. These two configuration gates plus the mandatory human approval step (captured as AC:H/UI:R) are the primary limiting factors; the attack itself needs no authentication (PR:N) and is delivered over the network.

Impact

Moderate real-world risk despite the 7.5 'High' CVSS. The vendor vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H correctly captures that this is network-reachable and unauthenticated (PR:N) but heavily tempered by AC:H and UI:R - the flaw only pays off after a human administrator approves the malicious registration (UI:R), and it is double-gated by two non-default settings (AC:H). Publicly available exploit code exists (WPScan e48789a3), which raises weaponization potential, but there is no EPSS score and no CISA KEV listing, so there is no evidence of active or automated exploitation - POC availability and active exploitation are distinct signals and only the former is present here. The most significant limiter is procedural rather than technical: an alert admin reviewing a pending registration that requests the 'administrator' role should reject it, so success depends on the admin approving blindly. Net: a legitimate privilege-escalation bug worth patching on affected sites, but not a mass-exploitation emergency; prioritize where the role-selection plus open-registration combination is actually enabled.

Exploit ScenarioDerived

An attacker visits the public registration page of a WordPress site running the vulnerable plugin with role-selection and open registration enabled, and submits a registration request tampered to select the 'administrator' role instead of an offered low-privilege role. Public exploit code (WPScan) demonstrates the request forgery. When the site administrator approves the pending registration - potentially without scrutinizing the requested role - the attacker's account is granted full administrator privileges.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 17, 2026

Privilege escalation in the WordPress plugin "Choose User Role at Registration" before 1.3.3 lets an unauthenticated visitor submit a registration request naming any role - including administrator - because the plugin never validates the requested role against the roles the administrator actually configured to be offered; once the pending request is approved, the attacker receives that elevated role. Exploitation requires both non-default features to be enabled (role selection at registration and public/open account registration), and the escalation only completes after a human administrator approves the account, which is why the assessed vector carries AC:H and UI:R despite the network-delivered, unauthenticated (PR:N) request. Publicly available exploit code exists and the vendor has released a patched version, but no confirmed active exploitation (CISA KEV) is associated with this CVE at time of analysis.

RemediationAI

Vendor-released patch: upgrade the "Choose User Role at Registration" plugin to version 1.3.3 or later, which is the fix referenced by the WPScan advisory (https://wpscan.com/vulnerability/e48789a3-49b4-4fa4-8243-c242b79b9d9d/); verify the installed version after updating, because the CPE data carries no version bound and cannot be used for detection. If the update cannot be applied immediately, the two configuration gates give concrete compensating controls: disable the plugin's role-selection-at-registration feature, which removes the attacker-controlled role parameter entirely (side effect: registrants can no longer choose their own role), or disable public/open account registration under WordPress Settings > General, which makes the vulnerable workflow unreachable (side effect: no self-service signup at all). As an interim hardening measure, restrict the roles offered to the lowest-privilege option (e.g. Subscriber only) and require administrators to manually inspect every pending registration request, rejecting any request that names an elevated role - this blocks the attack at the mandatory approval step (UI:R), but it depends entirely on reviewer diligence and offers no protection if an admin auto-approves or batch-approves requests. Additional defense-in-depth: audit existing users for unexpected administrator accounts created through the registration workflow, and monitor WordPress user-creation events for role changes to administrator. Do not rely on generic WAF rules as the primary mitigation, since the malicious request is a legitimate-looking registration submission.

Affected VersionsENISA

Choose User Role at Registration 0 <1.3.3

Affected Packages

euvd choose_user_role_at_registration fix: 1.3.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin that extends the built-in wp-login.php / wp-signup registration flow with a user-facing role selector and a pending-approval queue. WordPress itself defines roles and their capability sets (subscriber, contributor, author, editor, administrator) in wp_roles(), and any plugin that accepts a role value from the client side is responsible for validating that value server-side against an allow-list; CVE-2026-85128 is a CWE-269 improper privilege management failure, i.e. the plugin trusts the attacker-controlled role parameter at registration and applies it verbatim when the pending user is approved, instead of constraining it to the roles the site administrator enabled in the plugin's settings. The result is vertical privilege escalation to administrator, which in WordPress is equivalent to full site compromise (theme/plugin editor, arbitrary option changes, user management). The CPE record (cpe:2.3:a:unknown:choose_user_role_at_registration:*:*:*:*:*:*:*:*) reflects only a wildcarded version range with an unmapped vendor, so version-based scanning should rely on the plugin slug and the EUVD range "0 < 1.3.3" rather than the CPE. EUVD-2026-81336 covers the same range.

Know when Choose User Role At Registration gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 7.5 HIGH
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

Unauthenticated network request (PR:N/AV:N) but AC:H for the dual non-default config gate and UI:R because a separate admin approval action is required; success yields full admin so C/I/A:H.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 17, 2026 - 13:22 NVD
7.5 (HIGH)
Patch available
Sep 17, 2026 - 07:00 EUVD
CVE Published
Sep 17, 2026 - 06:00 cve.org
HIGH 7.5
CVE Published
Sep 17, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Choose User Role at Registration WordPress plugin before 1.3.3 does not validate the role requested at registration against the roles an administrator chose to offer, allowing unauthenticated users to request any role, including administrator, and to be granted it once the request is approved. Exploitation requires the Choose User Role at Registration WordPress plugin before 1.3.3's role selection feature and public account registration to both be enabled.

Technical POC Analysis

CWE-269 (Improper Privilege Management).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity privilege escalation flaw in the WordPress plugin "Choose User Role at Registration" (versions before 1.3.3) could allow an outside visitor to request an administrator-level account during self-registration, which an approving administrator may then unknowingly grant. Any organization running this plugin on an internet-facing WordPress site with open registration and role selection enabled is exposed, and because account approval is a routine administrative action, the escalation can occur without any obvious warning sign. Leadership should treat this as a governance risk over who holds privileged access to public-facing web properties, not merely a plugin maintenance item.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche WordPress registration-role plugin, limited install base
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy