HomeWordPress vulnerabilitiesPaytm Payment Gateway
Paytm Payment Gateway vulnerabilities
Paytm Payment Gateway has 3 known vulnerabilities in this database. The most recent published record is dated 2 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- 3,000+
- Latest version
- 2.8.9
- Last updated
- 23 Sep 2026
- Most recent
- 2 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-81740 | Medium 5.3 | Before 2.8.9 | Fixed in 2.8.9 | 5 d ago |
| SQL injection CVE-2026-81809 | High 7.5 | Before 2.8.9 | Fixed in 2.8.9 | 6 d ago |
| Cross-site scripting (XSS) CVE-2026-81739 | High 7.5 | Before 2.8.9 | Fixed in 2.8.9 | 6 d ago |
Read the published descriptions
- CVE-2026-81740, 2 Oct 2026
- The Paytm Payment Gateway WordPress plugin before 2.8.9 does not verify that payment callbacks genuinely originate from the payment provider when its secret key has not been configured, which is its state immediately after activation, allowing unauthenticated attackers to change the status of arbitrary orders, including marking unpaid orders as paid and reducing stock. CVE record
- CVE-2026-81809, 1 Oct 2026
- 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. CVE record
- CVE-2026-81739, 1 Oct 2026
- The Paytm Payment Gateway WordPress plugin before 2.8.9 does not sanitize and escape data it stores from payment callbacks before outputting it in an admin page, and the integrity check on those callbacks can be forged when the gateway is enabled without credentials, allowing unauthenticated users to store scripts that will run in the session of a store administrator. CVE record
What to do if you run Paytm Payment Gateway
If you run Paytm Payment Gateway, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Paytm Payment Gateway vulnerabilities
Free. We email you when a new vulnerability is published for Paytm Payment Gateway, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.