# CVE-2025-15475: Missing authorization in PayHere Payment Gateway

> Unauthenticated attackers can modify pending WooCommerce order statuses to paid or completed due to missing authorization checks in the PayHere 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:** 14 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-28q4-mjmf-52qp

## What is CVE-2025-15475?

CVE-2025-15475 is a medium-severity missing authorization vulnerability in PayHere Payment Gateway, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PayHere Payment Gateway Plugin for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to an improper validation logic in the check_payhere_response function in all versions up to, and including, 2.3.9. This makes it possible for unauthenticated attackers to change the status of pending WooCommerce orders to paid/completed/on hold.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-15475 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15475 is a medium-severity missing authorization vulnerability in PayHere Payment Gateway, published on 14 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-15475 in the wild and no public exploit code.

Affected product: PayHere 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-2025-15475/ (Markdown: https://insights.sbomify.com/CVE-2025-15475/index.md)
```

## Sources

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

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