# CVE-2026-94271: Deema Payment Gateway <= 1.1.2 - Unauthenticated Payment Confirmation Forgery via Unverified Success Return

> Unauthenticated attackers can forge payment confirmations to mark orders as paid without actual payment, affecting WordPress sites using this 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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-hv5c-cx33-qjj9

## What is CVE-2026-94271?

CVE-2026-94271 is a medium-severity vulnerability in Unknown Deema Payment Gateway, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Deema Payment Gateway WordPress plugin through 1.1.2 does not verify the payment with the payment provider when handling the return from the hosted checkout, and does not check the payment status or amount, allowing unauthenticated users to have orders marked as paid without any payment being taken.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-94271 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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