Paytm Payment Gateway
paytm-payments · plugin
Known security vulnerabilities for Paytm Payment Gateway. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 critical · 4 exploitable without logging in · 2 with public exploit code · latest Oct 2, 2026
Before you install
Use with care
- 3 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 2.8.9 · last updated Sep 23, 2026 · 3K+ installs
wordpress.org status checked on Nov 16, 2026
Vulnerabilities
- Critical 9.8
CVE-2022-45805high privilege≤ 2.7.3
WordPress Paytm Payment Gateway Plugin <= 2.7.3 is vulnerable to SQL Injection
- High 7.5
CVE-2026-81809unauthenticated→ 2.8.9
Paytm Payment Gateway < 2.8.9 - Unauthenticated SQLi via Payment Callback
- High 7.5
CVE-2026-81739unauthenticated · needs a click→ 2.8.9
Paytm Payment Gateway < 2.8.9 - Unauthenticated Stored XSS via Payment Callback
- Medium 6.5
CVE-2022-45362unauthenticated≤ 2.7.0
WordPress Paytm Payment Gateway Plugin <= 2.7.0 is vulnerable to Server Side Request Forgery (SSRF)
- Medium 5.3
CVE-2026-81740unauthenticated→ 2.8.9
Paytm Payment Gateway < 2.8.9 - Unauthenticated Order Status Manipulation via Payment Callback
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.