Payment Forms for Paystack <= 4.0.5 - Authenticated (Subscriber+) Information Exposure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Payment Forms for Paystack
- Affected Version
<= 4.0.5- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-66444
At a glance
CVE-2026-66444 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Payment Forms for Paystack WordPress plugin, affecting versions <= 4.0.5. 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. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Muhan Luo.
Vulnerability Overview
The Payment Forms for Paystack plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.0.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive user or configuration data.
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
Reaching this weakness in Payment Forms for Paystack <= 4.0.5 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. No fixed build of this plugin is recorded for Payment Forms for Paystack yet, so installs running <= 4.0.5 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
No patched version is recorded yet, so there is nothing to update to; WordSec's vulnerability alerts flag this record the moment that changes.
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C