# CVE-2025-14461: Xendit Payment <= 6.0.2 - Missing Authorization to Unauthenticated Arbitrary Order Status Update to Paid

> Unauthenticated attackers can fraudulently mark WooCommerce orders as paid via an unprotected callback endpoint, causing financial loss and inventory depletion.

- **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:** 4 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-67mq-622x-pqvh

## What is CVE-2025-14461?

CVE-2025-14461 is a medium-severity missing authorization vulnerability in tpixendit Xendit Payment, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Xendit Payment plugin for WordPress is vulnerable to unauthorized order status manipulation in all versions up to, and including, 6.0.2. This is due to the plugin exposing a publicly accessible WooCommerce API callback endpoint (`wc_xendit_callback`) that processes payment callbacks without any authentication or cryptographic verification that the requests originate from Xendit's payment gateway. This makes it possible for unauthenticated attackers to mark any WooCommerce order as paid by sending a crafted POST request to the callback URL with a JSON body containing an `external_id` matching the order ID pattern and a `status` of 'PAID' or 'SETTLED', granted they can enumerate order IDs (which are sequential integers). This leads to orders being fraudulently marked as completed without any actual payment, resulting in financial loss and inventory depletion.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14461 is a medium-severity missing authorization vulnerability in tpixendit Xendit Payment, published on 4 Feb 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-14461 in the wild and no public exploit code.

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

## Sources

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

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