Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister self-service low-privilege account
-
DeliveryAuthenticate to REST API
-
ExploitCall unrestricted user-meta update route
-
ExecutionSet own role to administrator
-
ImpactFull site compromise
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 that the WordPress site has user self-registration enabled so an attacker can obtain the needed low-privilege account (the description specifically cites a customer-type account), and that the Mobile builder plugin version 1.4.2 or earlier is installed and its vulnerable REST route is reachable. The core flaw is that the plugin fails to restrict which user meta keys a logged-in user may update through that REST route, so an authenticated low-privilege user can write the meta key(s) controlling role/capabilities. Limiting factors: authentication as a registered user is required (PR:L, so not fully unauthenticated), and sites that disable open registration raise the barrier to entry, though any existing low-privilege user can still exploit it. No user interaction by an admin is required (UI:N). |
| Impact | This is a genuine high-priority vulnerability, not an inflated CVSS score. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8) aligns closely with the description: a network-reachable REST route, low attack complexity, and only a low-privilege self-registered account needed (PR:L) to achieve full administrator takeover, which justifies the High confidentiality, integrity, and availability impacts. Supporting signals are mixed but net toward real concern: a public exploit exists (POC available, via WPScan) and SSVC rates Technical Impact as 'total,' which matches privilege escalation to admin. However, SSVC also reports Exploitation as 'none' (no observed in-the-wild activity) and Automatable as 'no,' and there is no CISA KEV listing and no EPSS score in the input. The absence of EPSS data means the statistical exploitation-likelihood signal cannot be weighed here. Net assessment: a straightforward, low-barrier privilege-escalation flaw with public exploit code - treat as high priority for any site running this plugin - but current evidence points to opportunity rather than confirmed mass exploitation. The main mitigating factor is prevalence: this is a niche plugin from an unidentified vendor, so the real-world blast radius is likely limited. |
| Exploit ScenarioDerived | An attacker registers a normal low-privilege account (e.g., a customer) on a WordPress site running the Mobile builder plugin, which is permitted by the site's self-registration. They then send a crafted request to the vulnerable REST route to update an unrestricted user meta key, setting their own capabilities/role to administrator and gaining full control of the site. Public exploit code referenced by WPScan lowers the skill barrier for this attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Privilege escalation in the Mobile Builder WordPress plugin (versions through 1.4.2) allows any authenticated low-privilege user - including a self-registered customer account - to grant themselves the administrator role by writing unrestricted user meta keys through one of the plugin's REST routes. The flaw requires only a valid low-privilege account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) and no administrator interaction, and publicly available exploit code exists according to WPScan. Sites with open user self-registration enabled are the easiest to attack, but any existing low-privilege user can still exploit the vulnerable route; CISA's SSVC rates technical impact as total while noting no observed exploitation and no known automatable exploitation at this time.
RemediationAI
No vendor-released patch was identified at time of analysis, so the most reliable action is to deactivate and remove the Mobile Builder plugin from any WordPress site where it is not strictly required until a fixed version is published; if the plugin is business-critical, treat the exposure as unmitigated and monitor the WPScan advisory for a patched release. Where removal is not immediately possible, reduce the attack surface by disabling open user self-registration (Settings > General > Membership) so attackers cannot mint the low-privilege account the exploit needs - this raises the barrier but does not protect sites where any existing subscriber/customer account could be abused, and it may break legitimate customer onboarding. Additionally, block or restrict access to the plugin's REST namespace at the web server or WAF layer (deny requests to the plugin's REST routes for non-administrator roles) and audit existing users for unexpected administrator accounts or tampered wp_capabilities meta; note that WAF rules can cause false positives for legitimate plugin functionality and must be validated before enforcement. Rotate credentials and review user roles after any suspected exposure, since the same meta-write primitive could be used to alter other user attributes beyond the role.
Affected VersionsENISA
Affected Packages
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 vulnerability is a classic CWE-269 (Improper Privilege Management) failure in a WordPress plugin. WordPress stores a user's role and capabilities in the usermeta table, most importantly under the wp_capabilities key (and the legacy wp_user_level key). Mobile Builder exposes a REST API route intended for logged-in users that accepts user meta updates, but it does not restrict or allowlist which meta keys a caller may write. Because the route authenticates the request only as a low-privilege user, an attacker can supply the capability meta key directly and set the value to administrator, escalating privileges without needing administrative approval or user interaction. The CPE data records the component as an unversioned/unknown-vendor entry (cpe:2.3:a:unknown:mobile_builder:*:*:*:*:*:*:*:*), which reflects that this is a third-party WordPress plugin rather than a tracked core product; ENISA's EUVD lists affected versions as Mobile builder 0 through 1.4.2. The underlying weakness is not a memory-safety or injection class bug but a missing authorization/validation check that should have compared the requested meta key against a permitted set or required the 'edit_users' capability.
Know when Mobile Builder 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
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network REST route (AV:N), no special conditions (AC:L), requires a low-privilege self-registered account (PR:L), no user interaction (UI:N); admin takeover yields full C/I/A impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Mobile builder WordPress plugin through 1.4.2 does not properly restrict which user meta keys a logged-in user can update through one of its REST routes, allowing any user with a self-registered account, such as a customer, to grant themselves the administrator role.
Technical POC Analysis
Evidence base: the WPScan advisory only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The Mobile Builder plugin for WordPress, in all versions through 1.4.2, contains a high-severity privilege escalation flaw that allows anyone holding even a basic account - such as a self-registered customer - to promote themselves to site administrator. No vendor patch exists and publicly available exploit code exists, so any organization running this plugin on an internet-facing site, particularly one with open user registration, faces full site takeover including customer data theft, content manipulation, and potential use of the site as a launch point against others.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall Mobile Builder through 1.4.2; disable open user self-registration and remove unused low-privilege accounts; block or restrict the plugin's vulnerable REST route via WAF, reverse proxy, or web server rules; enforce multi-factor authentication and least privilege for administrator accounts; monitor and alert on unexpected administrator role assignments and user meta changes; treat any site running the plugin with public exploit code available as potentially compromised and conduct a compromise assessment.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Mobile Builder
View allUnauthenticated SQL injection in the Mobile builder WordPress plugin (all versions through 1.4.2) lets any remote attack
SQL injection in the Mobile Builder WordPress plugin (versions through 1.4.2) lets unauthenticated remote attackers read
EUVD-2026-96736
GHSA-jm9q-87xx-cg6m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB