rootpwn

high · CVSS v3 7.5

CVE-2026-81740

The Paytm Payment Gateway WordPress plugin before 2.8.9 fails to verify payment callbacks when the secret key is not configured, allowing at

Overview

The Paytm Payment Gateway WordPress plugin before 2.8.9 fails to verify payment callbacks when the secret key is not configured, allowing attackers to spoof callbacks. This can lead to unauthorized order status changes and inventory manipulation. It affects sites using the plugin immediately after activation.

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.

Impact

Confidentiality: attackers can alter order data; Integrity: unauthorized order status changes; Availability: potential stock depletion. Defenders: WordPress site owners, e-commerce managers, payment gateway administrators.

Remediation

Update the plugin to version 2.8.9 or later. Ensure the secret key is configured before activation. Verify that callback verification is enabled. Monitor order logs for suspicious status changes.

Risk context

High severity (CVSS 7.5). Immediate attention recommended; no EPSS data available.

Affected products

  • Paytm Payment Gateway WP plugin

Scores

Severity
high
CVSS v2
5
CVSS v3
7.5
CVSS v4
—
EPSS
—

wordpress payment-gateway callback unauthenticated order-manipulation plugin-vulnerability high-severity

← All CVEs

Related CVEs

high

CVE-2026-103766

ClipBucket v5 through 5.5.3-#197 contains an sql injection vulnerability that allows authenticated users with ad_manager_access permission to inject SQL via the delete parameter in admin_area/ads_manager.php. Attackers can supply time-based blind payloads concatenated into AdsManager::DeleteAd queries to extract user credentials and emails or modify and delete arbitrary records.

View analysis

high

CVE-2026-103096

API key is hardcoded and retrievable from the application package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key.

View analysis

high

CVE-2026-103097

CVE-2026-103097 exposes a hardcoded API key in an Android application, allowing attackers to extract the key via reverse engineering. This enables unauthorized use of the API, potentially compromising user data and services. The vulnerability is high severity with a CVSS score of 7.5.

View analysis

high

CVE-2026-103098

Transmission of a sensitive key in the URL over an unencrypted HTTP connection. The request is sent over HTTP rather than HTTPS, meaning the key is transmitted in plaintext across the network. An attacker with the ability to monitor network traffic could intercept the request and obtain the key

View analysis