Product Stock Manager < 1.0.5 - Missing Authorization and Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.0.5
- Affected Plugin
- Product Stock Manager
- Affected Version
< 1.0.5- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-3451
At a glance
CVE-2022-3451 is a high-severity Missing Authorization vulnerability in the Product Stock Manager WordPress plugin, affecting versions < 1.0.5. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.0.5; sites on affected versions should update now. Disclosed October 2022, reported by WPScanTeam.
Vulnerability Overview
The Product Stock Manager plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on several AJAX actions such as af_sm_set_checkbox_status in versions up to, and including, 1.0.5. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke those actions and make changes they are unauthorized to do so. Furthermore, proper Cross-Site Request Forgery protection is missing. This allows unauthenticated attackers to invoke those actions, via forged request granted they can trick a user into clicking on a link. The af_sm_set_checkbox_status AJAX action can be used to change arbitrary options on the site, which can be used to register administrative user accounts on the site.
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.
CWE-862: Missing Authorization
Reaching this weakness in Product Stock Manager < 1.0.5 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 Product Stock Manager the fix is 1.0.5: builds < 1.0.5 are affected, anything from 1.0.5 onward is not.
Remediation
Update to version 1.0.5, 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: Product Stock Manager 1.0.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C