Skip to main content

Telcell Payment Gateway CVE-2026-103301

| EUVDEUVD-2026-107142 MEDIUM
Insufficient Verification of Data Authenticity (CWE-345)
2026-10-21 WPScan GHSA-mcx5-9495-x4v5
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Place order on target WooCommerce store
  2. Delivery
    Craft forged payment notification
  3. Exploit
    Sign with empty default secret
  4. Execution
    Submit to notification handler
  5. Impact
    Order marked paid without payment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
Exploitation Conditions

Exploitable against default configurations because the notification-signing secret is empty by default, so an attacker can compute a 'valid' signature without knowing any secret - no authentication, user interaction, or non-default setup is required. The specific prerequisites are: the Payment Gateway for Telcell plugin at a version before 2.0.5 is active, WooCommerce is in use, and the plugin's payment-notification/callback endpoint is network-reachable. The main limiting factor is that an administrator who has manually configured a non-empty signing secret would break the trivial forgery; otherwise the only practical constraint is the small deployment footprint of this regional gateway.

Impact

This is a genuine but moderate-severity business-logic flaw, not a critical mass-exploitation threat. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3) is internally consistent with the description: remote, unauthenticated, no user interaction, low integrity impact and no confidentiality or availability impact. The core weakness - an empty default signing secret allowing forged payment notifications - means exploitation is trivial against any default installation, so attack complexity is correctly Low. A public exploit exists (WPScan), raising practical risk above the raw score. However, key triage signals are MISSING: no EPSS score and no KEV listing were provided, so there is no evidence of widespread or active exploitation; POC availability is NOT equivalent to active exploitation. The real-world risk is tightly bounded by prevalence - this is a niche regional (Telcell/Armenian) payment gateway plugin, so the absolute population of exploitable sites is small. Net: prioritize patching on any affected store because the financial-fraud impact (goods shipped against unpaid orders) is direct, but this is not a broad-internet emergency. Note the input 'Information Disclosure' tag conflicts with the actual impact, which is integrity/order-state manipulation, not disclosure (C:N in the vector confirms no confidentiality loss).

Exploit ScenarioDerived

An attacker identifies a WooCommerce store running the Telcell gateway with the default (empty) secret, places an order, then sends a forged payment-notification request with a valid signature computed against the empty secret, flipping the order to 'paid' so goods or services are released without payment. A public proof-of-concept from WPScan demonstrates the forgery, and the same handler can be abused to mark a victim's chosen order 'failed' with an invalid signature. Because the flaw is network-reachable and unauthenticated with low complexity, no special tooling or access is needed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Unauthenticated payment-notification forgery in the Payment Gateway for Telcell WordPress plugin (versions before 2.0.5) allows remote attackers to mark arbitrary WooCommerce orders as paid, because the secret used to sign incoming callbacks is empty by default and therefore trivially reproducible. The same callback handler can also flip an attacker-chosen order to failed when an invalid signature is supplied, giving a second abuse path. Publicly available exploit code exists; there is no CISA KEV entry, and the impact is bounded to integrity of order/payment state (CVSS 5.3, I:L only), with risk concentrated on stores that leave the gateway at default settings.

RemediationAI

Vendor-released patch: upgrade the Payment Gateway for Telcell plugin to version 2.0.5 or later, which is the fixed release referenced by the WPScan advisory (https://wpscan.com/vulnerability/c3b5f5fb-cddf-47f3-b39f-8bcd2c738c83/). If upgrading immediately is not possible, the highest-value compensating control is to open the gateway settings and set a non-empty, high-entropy signing secret shared with Telcell - this restores meaningful signature verification, at the trade-off that a mismatched secret will cause legitimate Telcell notifications to be rejected and orders to stay pending until reconciled manually. As a stop-gap, restrict the gateway callback endpoint at the WAF or reverse proxy so only Telcell's published notification source addresses can reach it, accepting that IP changes on the provider side will silently break payment confirmation. Where the gateway is not actively used, disable the Telcell payment method entirely to remove the endpoint. Regardless of mitigation, reconcile order status against the Telcell merchant portal for the exposure window, since forged 'paid' and 'failed' transitions leave no reliable trace in the plugin itself.

Affected VersionsENISA

Payment Gateway for Telcell 0 <2.0.5

Affected Packages

euvd payment_gateway_for_telcell fix: 2.0.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The plugin implements a WooCommerce payment gateway for the Telcell regional payment provider: Telcell posts a server-to-server payment notification to a plugin callback URL, which the plugin must authenticate before mutating order status. Signature verification here depends on a shared secret that ships as an empty string in the default configuration, so the expected signature can be computed by anyone without knowledge of any key - the check is present but provides no assurance. This is a business-logic / improper-verification-of-authenticity class issue (closest to CWE-345/CWE-347 for missing or ineffective signature verification, compounded by an insecure default of CWE-1188); the input data records CWE as not assigned. The CPE string uses an 'unknown' vendor with the wildcard version range, so inventory matching is best done by the WordPress plugin slug rather than CPE. Exploitation only needs network reachability to the gateway's notification endpoint and an existing order ID to target; no account, nonce, or user interaction is involved, matching the CVSS vector AV:N/AC:L/PR:N/UI:N.

Know when Payment Gateway For Telcell gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Remote unauthenticated forgery via empty default secret gives AV:N/AC:L/PR:N/UI:N; impact is order-state tampering only, so I:L with C:N and A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch available
Oct 21, 2026 - 10:16 EUVD
CVE Published
Oct 21, 2026 - 08:38 cve.org
MEDIUM 5.3

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche regional (Armenian Telcell) WooCommerce payment plugin, limited installs
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy