CVE-2026-104799 — WordPress
HIGHCVE-2026-104799 is a high-severity (CVSS 8.8) Improper Privilege Management vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
The Mobile builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.4.2 via the `wcfmmp_profile_settings()` REST handler exposed at…
Description
The Mobile builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.4.2 via the wcfmmp_profile_settings() REST handler exposed at POST /mobile-builder/v1/wcfm-profile-settings. This is due to a PHP loose-comparison logic flaw in the meta key allow-list check — strpos( $key, 'mobile_builder' ) == 0 evaluates to true for any key that does not contain the substring 'mobile_builder' because strpos() returns false on no match and false == 0 is true in PHP — combined with a permission_callback (user_permissions_check) that grants access to any authenticated user by only verifying $user->exists(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to pass an unsanitized data array via the key and data parameters directly to update_user_meta(), overwriting arbitrary user meta on their own account — including the wp_capabilities meta key — to grant themselves Administrator-level privileges.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
The records we use list no fixed release for CVE-2026-104799. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-104799 in your dependencies?
Find it across your dependency tree, including transitive dependencies.