Download Manager and Payment Form WordPress Plugin – WP SmartPay 1.1.0 - 2.7.13 - Authenticated (Subscriber+) Information Exposure
Strategic Overview
- Status
- Patched in 2.8.0
- Affected Version
1.1.0 – 2.7.13- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-3851
At a glance
CVE-2025-3851 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPSmartPay WordPress plugin, affecting versions 1.1.0 – 2.7.13. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). 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 May 2025, reported by kr0d.
Vulnerability Overview
The Download Manager and Payment Form WordPress Plugin – WP SmartPay plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions 1.1.0 to 2.7.13 via the show() function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view other user's data like email address, name, and notes.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
WPSmartPay 1.1.0 – 2.7.13 carries this weakness at show(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WPSmartPay the fix is 2.8.0: builds 1.1.0 – 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?
The fix is the thing that ends this: WPSmartPay 2.8.0 closes this, and updating the plugin is the step that ends it.
- 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