WP Shamsi <= 4.1.1 - Missing Authorization to Plugin Settings Update
Strategic Overview
- Status
- Patched in 4.2.0
- Affected Plugin
- WP Shamsi – افزونه تاریخ شمسی و فارسی ساز وردپرس
- Affected Version
<= 4.1.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-38058
At a glance
CVE-2022-38058 is a medium-severity Missing Authorization vulnerability in the WP Shamsi WordPress plugin, affecting versions <= 4.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.2.0; sites on affected versions should update now. Disclosed September 2022, reported by Muhammad Daffa.
Vulnerability Overview
The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check when saving plugin settings in versions up to, and including, 4.1.1. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to update the plugin's options and active a pro license.
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
Reaching this weakness in WP Shamsi <= 4.1.1 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.2.0: builds <= 4.1.1 are affected, anything from 4.2.0 onward is not.
Remediation
Update to version 4.2.0, 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.2.0 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