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


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-j9j3-7vxw-jm6j

## What is CVE-2026-103302?

CVE-2026-103302 is a medium-severity vulnerability in Unknown Payment Gateway for Idram, published on 21 Oct 2026. 

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-103302?


## How do I fix CVE-2026-103302?

No fix has been published for CVE-2026-103302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103302 being exploited?

There is no known exploitation of CVE-2026-103302 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103302 and fix it if it is affected.

What it is: CVE-2026-103302 is a medium-severity vulnerability in Unknown Payment Gateway for Idram, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103302 in the wild and no public exploit code.

Affected product: Unknown Payment Gateway for Idram. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103302/ (Markdown: https://insights.sbomify.com/CVE-2026-103302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103302
- OSV: https://osv.dev/vulnerability/CVE-2026-103302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103302/
Summaries are generated and may contain mistakes; the official description above is the record.