# CVE-2026-106010: BDM Digital Payment Gateway 1.2.7 - 1.3.12 - Unauthenticated Payment Confirmation Forgery

> Unauthenticated attackers can forge payment confirmations to mark WooCommerce orders as paid without actual payment due to missing credential verification.

- **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:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-3qp2-cxv4-63f4

## What is CVE-2026-106010?

CVE-2026-106010 is a medium-severity missing authorization vulnerability in Unknown BDM Digital Payment Gateway, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BDM Digital Payment Gateway WordPress plugin through 1.3.12 does not verify the credentials on its public payment-status update route and treats unset credentials as valid, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without payment in the default configuration.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106010 is a medium-severity missing authorization vulnerability in Unknown BDM Digital Payment Gateway, published on 19 Oct 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-106010 in the wild and no public exploit code.

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

## Sources

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

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