CVE-2026-81740: Paytm Payment Gateway (WordPress plugin) · Improper Authentication
Affects Paytm Payment Gateway (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.8.9 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.8.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Paytm Payment Gateway (WordPress plugin) to 2.8.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Paytm Payment Gateway | Affected
| Fixed in
|
AI-suggested
Upgrade the Paytm Payment Gateway WordPress plugin to version 2.8.9 or later, where this authentication issue has been addressed. Until the upgrade, ensure the secret key is properly configured immediately after plugin activation to prevent exploitation.
Description
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.