Plugins · direct-payments-wp · data as of 2026-11-04
Is Direct Payments WP safe? Known vulnerabilities and latest version
- Latest version
- 1.4.1
- Last updated
- 2026-07-27
- Active installs
- 50+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 7.0+
Direct Payments WP lets you easily accept payments via bank transfers, mobile money, and P2P platforms on your WordPress website. — by Digages
What to do
- Update to the latest version (1.4.1). Anything older than 1.3.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get direct-payments-wp --field=version shows what you run; wp plugin update direct-payments-wp updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.3 CVE-2025-49340 · published 2025-12-31
Information disclosure in Direct Payments WP (1.3.2 and older)
- Affected
- 1.3.2 and older
- Fixed in
- 1.3.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Digages Direct Payments WP direct-payments-wp allows Retrieve Embedded Sensitive Data.This issue affects Direct Payments WP: from n/a through <= 1.3.2.
medium 4.3 CVE-2025-49339 · published 2025-12-31
Missing authorization check in Direct Payments WP (1.3.2 and older)
- Affected
- 1.3.2 and older
- Fixed in
- 1.3.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in Digages Direct Payments WP direct-payments-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Direct Payments WP: from n/a through <= 1.3.2.
Recent activity
- 2026-07-27 — latest release on wordpress.org (1.4.1).
- 2025-12-31 — Information disclosure disclosed (CVE-2025-49340), fixed in 1.3.3.
- 2025-12-31 — Missing authorization check disclosed (CVE-2025-49339), fixed in 1.3.3.
Get an email when Direct Payments WP has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Direct Payments WP (direct-payments-wp) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Sensitive data exposure (1) · Missing authorization (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/direct-payments-wp (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/direct-payments-wp"><img src="https://laskyr.com/plugins/direct-payments-wp/badge.svg" alt="Direct Payments WP vulnerability status"></a>