Content Mask <= 1.8.4 - Authenticated (Subscriber+) Arbitrary Options Update
Strategic Overview
- Status
- Patched in 1.8.4.1
- Affected Plugin
- Content Mask
- Affected Version
<= 1.8.4- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-1203
At a glance
CVE-2022-1203 is a high-severity Missing Authorization vulnerability in the Content Mask WordPress plugin, affecting versions <= 1.8.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.8.4.1; sites on affected versions should update now. Disclosed May 2022, reported by ptsfence.
Vulnerability Overview
The Content Mask WordPress plugin before 1.8.4.1 does not have authorisation and CSRF checks in various AJAX actions, as well as does not validate the option to be updated to ensure it belongs to the plugin. As a result, any authenticated user, such as subscriber could modify arbitrary blog options
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in Content Mask <= 1.8.4 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 Content Mask the fix is 1.8.4.1: builds <= 1.8.4 are affected, anything from 1.8.4.1 onward is not.
Remediation
Update to version 1.8.4.1, 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: Content Mask 1.8.4.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C