CVE-2026-103302

Payment Gateway for Idram < 2.1.6 - Unauthenticated Arbitrary Order Status Manipulation

2026-10-19 00:00
Naoki Kawahigashi

Strategic Overview

Status
Patched in 2.1.6
Affected Version
< 2.1.6
CVSS
5.3Medium
Weakness type
CWE-345 · Insufficient Verification of Data Authenticity
CVE
CVE-2026-103302
View all Payment Gateway for Idram vulnerabilities

At a glance

CVE-2026-103302 is a medium-severity Insufficient Verification of Data Authenticity vulnerability in the Payment Gateway for Idram WordPress plugin, affecting versions < 2.1.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.6; sites on affected versions should update now. Disclosed October 2026, reported by Naoki Kawahigashi.

Vulnerability Overview

The Payment Gateway for Idram plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in all versions up to 2.1.6. This is due to missing validation that the merchant secret key and receiving account are non-empty before accepting and verifying payment notification checksums, allowing an empty-string-based HMAC to be trivially reproduced, and absence of authentication on the failure webhook endpoint. This makes it possible for unauthenticated attackers to mark arbitrary orders as paid by forging a valid payment notification checksum, and force arbitrary orders into a failed state without any authentication.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-345: Insufficient Verification of Data Authenticity

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Remediation

Update to version 2.1.6, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Payment Gateway for Idram 2.1.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C