Mesmerize Companion <= 1.6.158 - Missing Authorization Authenticated (Subscriber+) Settings Update
Strategic Overview
- Status
- Patched in 1.6.162
- Affected Plugin
- Mesmerize Companion
- Affected Version
<= 1.6.158- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12027
At a glance
CVE-2025-12027 is a medium-severity Missing Authorization vulnerability in the Mesmerize Companion WordPress plugin, affecting versions <= 1.6.158. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.6.162; sites on affected versions should update now. Disclosed February 2026, reported by Rafshanzani Suhada.
Vulnerability Overview
The Mesmerize Companion plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the "openPageInCustomizer" and "openPageInDefaultEditor" functions in all versions up to, and including, 1.6.158. This makes it possible for authenticated attackers - with subscriber level access and above, on websites with the Mesmerize theme activated - to mark arbitrary pages as maintainable, wrap their content in custom sections, change page template metadata, and toggle the default editor flag without proper authorization.
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-862: Missing Authorization
Mesmerize Companion <= 1.6.158 carries this weakness at openPageInCustomizer, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Mesmerize Companion the fix is 1.6.162: builds <= 1.6.158 are affected, anything from 1.6.162 onward is not.
Remediation
Update to version 1.6.162, or a newer patched version
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. None of that substitutes for the fix: Mesmerize Companion 1.6.162 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Mesmerize Companion
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C