The Moneytizer <= 9.6.3 - Cross-Site Request Forgery via multiple AJAX actions
Strategic Overview
- Status
- Patched in 10.0.1
- Affected Plugin
- The Moneytizer
- Affected Version
<= 9.6.3- CVSS
- 8.1High
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2023-6968
At a glance
CVE-2023-6968 is a high-severity Improper Access Control vulnerability in the The Moneytizer WordPress plugin, affecting versions <= 9.6.3. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). The issue is fixed in version 10.0.1; sites on affected versions should update now. Disclosed June 2024, reported by Francesco Carlucci.
Vulnerability Overview
The The Moneytizer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 9.6.3. This is due to missing or incorrect nonce validation on multiple AJAX functions. This makes it possible for unauthenticated attackers to to update and retrieve billing and bank details, update and reset the plugin's settings, and update languages as well as other lower-severity actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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-284: Improper Access Control
Reaching this weakness in The Moneytizer <= 9.6.3 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For The Moneytizer the fix is 10.0.1: builds <= 9.6.3 are affected, anything from 10.0.1 onward is not.
Remediation
Update to version 10.0.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: The Moneytizer 10.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C