Peach Payments Gateway <= 3.1.9 - Missing Authorization via peach_core_version_rollback()
Strategic Overview
- Status
- Patched in 3.2.0
- Affected Plugin
- Peach Payments Gateway
- Affected Version
<= 3.1.9- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-25922
At a glance
CVE-2024-25922 is a medium-severity Missing Authorization vulnerability in the Peach Payments Gateway WordPress plugin, affecting versions <= 3.1.9. 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 3.2.0; sites on affected versions should update now. Disclosed February 2024, reported by Abdi Pranata.
Vulnerability Overview
The Peach Payments Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the peach_core_version_rollback() function in versions up to, and including, 3.1.9. This makes it possible for authenticated attackers, with subscriber-level access and above, to rollback the plugin's version.
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
Peach Payments Gateway <= 3.1.9 carries this weakness at peach_core_version_rollback(), 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 Peach Payments Gateway the fix is 3.2.0: builds <= 3.1.9 are affected, anything from 3.2.0 onward is not.
Remediation
Update to version 3.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: Peach Payments Gateway 3.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