# CVE-2026-16738: Conekta Payment Gateway < 6.2.2 - Unauthenticated Order Payment Completion via Webhook Forgery

> Unauthenticated attackers can forge webhooks to mark arbitrary orders as paid without actual payment, compromising financial integrity.

- **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:** 22 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** GHSA-4vwp-q9wh-xxq2

## What is CVE-2026-16738?

CVE-2026-16738 is a medium-severity vulnerability in Unknown Conekta Payment Gateway, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Conekta Payment Gateway WordPress plugin before 6.2.2 does not verify the authenticity of incoming payment gateway webhook notifications, nor bind the confirmed payment to the targeted order or verify its amount, allowing unauthenticated attackers to mark arbitrary orders as paid without payment.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-16738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16738 is a medium-severity vulnerability in Unknown Conekta Payment Gateway, published on 22 Aug 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-16738 in the wild and no public exploit code.

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

## Sources

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

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