Mobile builder <= 1.4.2 - Authenticated (Subscriber+) Privilege Escalation
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Mobile builder
- Affected Version
<= 1.4.2- CVSS
- 6.3Medium
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-103694
At a glance
CVE-2026-103694 is a medium-severity Improper Privilege Management vulnerability in the Mobile builder WordPress plugin, affecting versions <= 1.4.2. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Raphael P. Cigana.
Vulnerability Overview
The Mobile builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.4.2. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges beyond those intended for their role.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-269: Improper Privilege Management
Reaching this weakness in Mobile builder <= 1.4.2 takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. No fixed build of this plugin is recorded for Mobile builder yet, so installs running <= 1.4.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Mobile builder
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C