WP Shamsi <= 4.1.0 - Missing Authorization to Arbitrary Plugin Deactivation
Strategic Overview
- Status
- Patched in 4.1.1
- Affected Plugin
- WP Shamsi – افزونه تاریخ شمسی و فارسی ساز وردپرس
- Affected Version
<= 4.1.0- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-4555
At a glance
CVE-2022-4555 is a medium-severity Missing Authorization vulnerability in the WP Shamsi WordPress plugin, affecting versions <= 4.1.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.1.1; sites on affected versions should update now. Disclosed November 2022, reported by Chloe Chamberland.
Vulnerability Overview
The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the deactivate() function hooked via init() in versions up to, and including, 4.1.0. This makes it possible for unauthenticated attackers to deactivate arbitrary plugins on the site. This can be used to deactivate security plugins that aids in exploiting other vulnerabilities.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Shamsi <= 4.1.0 carries this weakness at deactivate(), and reaching it takes a caller who can reach the endpoint. 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 WP Shamsi the fix is 4.1.1: builds <= 4.1.0 are affected, anything from 4.1.1 onward is not.
Remediation
Update to version 4.1.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: WP Shamsi 4.1.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