WP SmartPay <= 2.7.13 - Authenticated (Subscriber+) Account Takeover
Strategic Overview
- Status
- Patched in 2.8.0
- Affected Version
<= 2.7.13- CVSS
- 8.8High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-25171
At a glance
CVE-2025-25171 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WPSmartPay WordPress plugin, affecting versions <= 2.7.13. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.8.0; sites on affected versions should update now. Disclosed June 2025, reported by Le Ngoc Anh.
Vulnerability Overview
The Download Manager and Payment Form WordPress Plugin – WP SmartPay plugin for WordPress is vulnerable to privilege escalation via account takeover in versions 1.1.0 to 2.7.13. This is due to the plugin not properly validating a user's identity prior to updating their email through the update() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.
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, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
WPSmartPay <= 2.7.13 carries this weakness at update(), and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WPSmartPay the fix is 2.8.0: builds <= 2.7.13 are affected, anything from 2.8.0 onward is not.
Remediation
Update to version 2.8.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: WPSmartPay 2.8.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPSmartPay – Payment Forms, Invoices, Donations & Subscriptions
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C