# CVE-2026-66444: WordPress Payment Forms for Paystack plugin <= 4.0.5 - Sensitive Data Exposure vulnerability

> Attackers can expose sensitive subscriber data in the Payment Forms for Paystack WordPress plugin, requiring an upgrade to secure user information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-wgmv-vvvj-jcfh

## What is CVE-2026-66444?

CVE-2026-66444 is a medium-severity vulnerability in kendysond Payment Forms for Paystack, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber Sensitive Data Exposure in Payment Forms for Paystack <= 4.0.5 versions.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-66444?


## How do I fix CVE-2026-66444?

No fix has been published for CVE-2026-66444 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-66444 being exploited?

There is no known exploitation of CVE-2026-66444 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66444 and fix it if it is affected.

What it is: CVE-2026-66444 is a medium-severity vulnerability in kendysond Payment Forms for Paystack, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66444 in the wild and no public exploit code.

Affected product: kendysond Payment Forms for Paystack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-66444/ (Markdown: https://insights.sbomify.com/CVE-2026-66444/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-66444
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-66444
- OSV: https://osv.dev/vulnerability/CVE-2026-66444

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-66444/
Summaries are generated and may contain mistakes; the official description above is the record.