CVE-2026-81740

Paytm Payment Gateway < 2.8.9 - Unauthenticated Order Status Manipulation via Payment Callback

  • Medium 5.3
  • A public exploit reference is listed

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.

Key facts

Published
2 Oct 2026
Last changed
2 Oct 2026
Assigned by
WPScan
EPSS
0.182% likely to be exploited in the next 30 days, higher than 7.811% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 3.1, Mediumfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
UnknownPaytm Payment Gateway
  • Default status: unaffected
  • 0 up to but excluding 2.8.9 (affected)

Timeline

  1. 2 Oct 2026 Published

Weakness

References