# CVE-2025-14078: PAYGENT for WooCommerce <= 2.4.6 - Missing Authorization to Unauthenticated Payment Callback Manipulation

> Unauthenticated attackers can manipulate payment callbacks and modify order statuses in the PAYGENT for WooCommerce plugin due to missing authorization checks.

- **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:** 17 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hj72-p4c8-2pp4

## What is CVE-2025-14078?

CVE-2025-14078 is a medium-severity missing authorization vulnerability in shoheitanaka PAYGENT for WooCommerce, published on 17 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PAYGENT for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.6. This is due to missing authorization checks on the paygent_check_webhook function combined with the paygent_permission_callback function unconditionally returning true on line 199. This makes it possible for unauthenticated attackers to manipulate payment callbacks and modify order statuses by sending forged payment notifications via the `/wp-json/paygent/v1/check/` endpoint.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-14078?


## How do I fix CVE-2025-14078?

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

## Is CVE-2025-14078 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14078 and fix it if it is affected.

What it is: CVE-2025-14078 is a medium-severity missing authorization vulnerability in shoheitanaka PAYGENT for WooCommerce, published on 17 Jan 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-2025-14078 in the wild and no public exploit code.

Affected product: shoheitanaka PAYGENT for WooCommerce. 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-2025-14078/ (Markdown: https://insights.sbomify.com/CVE-2025-14078/index.md)
```

## Sources

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

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