Paytm Payment Gateway: SQL injection
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. The authoritative export does not name the request parameter or handler beyond the affected feature described above. The authoritative export identifies the fixed release as 2.8.9.
- Component
- Paytm Payment Gateway
- Plugin slug
paytm-payment-gateway- Affected
- < 2.8.9
- Safe version
2.8.9- Published
- Oct 01, 2026
- Weakness
- Not assigned
This CVE was published Oct 01, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Paytm Payment Gateway to 2.8.9 or a later supported release. An application-level fix should parameterize database values and allowlist identifiers or sort fields that cannot be bound as values.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.