# CVE-2026-12972: PayPlus Payment Gateway < 8.2.2 - Unauthenticated Order Payment Metadata Tampering

> Unauthenticated attackers can tamper with payment metadata of arbitrary WooCommerce orders due to missing authorization checks in the PayPlus Payment Gateway 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:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-hhfq-j633-m72j

## What is CVE-2026-12972?

CVE-2026-12972 is a medium-severity missing authorization vulnerability in Unknown PayPlus Payment Gateway, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PayPlus Payment Gateway WordPress plugin before 8.2.2 does not perform authorization or order-ownership validation in one of its AJAX actions available to unauthenticated users, allowing them to tamper with the payment-related metadata of arbitrary WooCommerce orders.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-12972 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12972 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12972 is a medium-severity missing authorization vulnerability in Unknown PayPlus Payment Gateway, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12972 exists.

Affected product: Unknown PayPlus Payment Gateway. 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-12972/ (Markdown: https://insights.sbomify.com/CVE-2026-12972/index.md)
```

## Sources

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

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