Paytm Payment Gateway < 2.8.9 - Unauthenticated Order Status Manipulation via Payment Callback
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-287.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Paytm Payment Gateway | before 2.8.9 | 2.8.9 | Patch available | CNA |
- Paytm Payment Gateway VendorUnknown Affected before 2.8.9 Fixed in 2.8.9 Patch available CNA
Remediation
- Fix · CNA Paytm Payment Gateway (Unknown) Fixed in 2.8.9
Timeline
- 2026-10-02 Threatist record created from CVE-2026-81740
- 2026-10-03 Alias added: GHSA-2xw5-r48v-m7fg
References
Sources
- CVE-2026-81740 · CVE Program
- CVE-2026-81740 · NVD
- FIRST EPSS
- GHSA-2xw5-r48v-m7fg · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences