# CVE-2026-105989: Accept PayPal Payments using Contact Form 7 < 4.0.7 - Unauthenticated Transaction Status Forgery

> Unauthenticated attackers can forge transaction statuses and modify metadata on arbitrary posts due to missing authorization checks in the plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-29vq-ff64-7939

## What is CVE-2026-105989?

CVE-2026-105989 is a medium-severity missing authorization vulnerability in Unknown Accept PayPal Payments using Contact Form 7, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Accept PayPal Payments using Contact Form 7 WordPress plugin before 4.0.7 does not perform any authorization or request-validation checks on one of its AJAX actions, allowing unauthenticated attackers to forge the stored transaction status of records and to write the Accept PayPal Payments using Contact Form 7 WordPress plugin before 4.0.7's status metadata onto arbitrary posts.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-105989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105989 is a medium-severity missing authorization vulnerability in Unknown Accept PayPal Payments using Contact Form 7, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105989 in the wild and no public exploit code.

Affected product: Unknown Accept PayPal Payments using Contact Form 7. 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-105989/ (Markdown: https://insights.sbomify.com/CVE-2026-105989/index.md)
```

## Sources

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

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