What is the severity of CVE-2025-3851?

CVE-2025-3851 has a medium severity rating due to the risk of Insecure Direct Object References allowing unauthorized access to sensitive data.

How do I fix CVE-2025-3851?

To fix CVE-2025-3851, update the WP SmartPay plugin to version 2.7.14 or later, which addresses the validation issue.

What versions of WP SmartPay are affected by CVE-2025-3851?

WP SmartPay versions 1.1.0 to 2.7.13 are affected by CVE-2025-3851 due to the insecure coding practices.

Who is impacted by the CVE-2025-3851 vulnerability?

Authenticated users with access to the WP SmartPay plugin may be impacted by CVE-2025-3851, enabling potential unauthorized actions.

What is Insecure Direct Object Reference in the context of CVE-2025-3851?

Insecure Direct Object Reference in CVE-2025-3851 refers to the lack of proper validation on user-controlled keys, allowing unauthorized access to resources.

Vulnerability/
CVE-2025-3851

medium

4.3

CWE

200

EPSS

0.027%

7/5/2025

CVE-2025-3851: Download Manager and Payment Form WordPress Plugin – WP SmartPay 1.1.0 - 2.7.13 - Authenticated (Subscriber+) Information Exposure

First published: Wed May 07 2025(Updated: )

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.

Credit: security@wordfence.com

Affected Software	Affected Version	How to fix
WP SmartPay	>=1.1.0<=2.7.13

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2025-3851?
CVE-2025-3851 has a medium severity rating due to the risk of Insecure Direct Object References allowing unauthorized access to sensitive data.
How do I fix CVE-2025-3851?
To fix CVE-2025-3851, update the WP SmartPay plugin to version 2.7.14 or later, which addresses the validation issue.
What versions of WP SmartPay are affected by CVE-2025-3851?
WP SmartPay versions 1.1.0 to 2.7.13 are affected by CVE-2025-3851 due to the insecure coding practices.
Who is impacted by the CVE-2025-3851 vulnerability?
Authenticated users with access to the WP SmartPay plugin may be impacted by CVE-2025-3851, enabling potential unauthorized actions.
What is Insecure Direct Object Reference in the context of CVE-2025-3851?
Insecure Direct Object Reference in CVE-2025-3851 refers to the lack of proper validation on user-controlled keys, allowing unauthorized access to resources.

collector/mitre-cve
source/MITRE
agent/title
agent/weakness
agent/references
agent/description
agent/type
agent/first-publish-date
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
agent/softwarecombine
agent/severity
agent/author
agent/event
collector/nvd-api
source/NVD
agent/last-modified-date
collector/epss-latest
source/FIRST
agent/source
agent/tags
agent/epss
vendor/wp smartpay
canonical/wp smartpay

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.