Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94299 Overview
CVE-2026-94299 affects the elegro Crypto Payment WordPress plugin through version 1.0.1. The plugin fails to require a shared secret before trusting incoming payment notification requests. Unauthenticated attackers can forge payment confirmations and alter the status of arbitrary orders on any installation where the secret remains at its default empty value. The flaw is classified as an authorization issue [CWE-863].
Critical Impact
Remote unauthenticated attackers can mark arbitrary orders as paid, enabling fraudulent order fulfillment on affected WordPress stores.
Affected Products
- elegro Crypto Payment WordPress plugin versions up to and including 1.0.1
- WordPress sites with the plugin installed and the shared secret left empty
- WooCommerce-based storefronts integrating elegro Crypto Payment
Discovery Timeline
- 2026-10-06 - CVE-2026-94299 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-94299
Vulnerability Analysis
The elegro Crypto Payment plugin exposes a payment notification endpoint intended for callbacks from the payment processor. The endpoint is designed to validate a shared secret supplied with each callback to prove the request originated from the legitimate payment gateway. The plugin does not enforce that the shared secret has been configured before processing incoming requests. When the secret is left at its empty default, the comparison passes for any request, including requests supplied by an unauthenticated attacker.
An attacker who sends a crafted POST request to the notification endpoint can mark any order ID as paid. This bypasses the intended cryptographic verification and allows manipulation of order state without authentication. The impact is limited to order status data integrity and does not affect site availability, but it enables merchandise fraud against affected merchants.
Root Cause
The root cause is missing authorization logic around a security-sensitive handler. The plugin treats an unconfigured shared secret as a valid comparison target rather than refusing to process callbacks until the merchant provides a non-empty secret. This matches the [CWE-863] Incorrect Authorization pattern.
Attack Vector
Exploitation requires only network access to the WordPress site and knowledge of a target order identifier. No credentials, user interaction, or elevated privileges are needed. The attacker crafts a payment notification request matching the plugin's expected format and submits it to the plugin's callback URL. Refer to the WPScan Vulnerability Report for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-94299
Indicators of Compromise
- Unexpected transitions of WooCommerce orders to a paid or completed state without a corresponding on-chain crypto transaction
- Inbound HTTP POST requests to the elegro Crypto Payment callback endpoint from unfamiliar source IP addresses
- Order status changes occurring outside normal business hours or in rapid succession across unrelated order IDs
Detection Strategies
- Correlate WooCommerce order status change events with webserver access logs for the plugin's notification endpoint
- Alert on callback requests that lack the expected gateway source IP ranges published by elegro
- Review the plugin configuration to confirm whether the shared secret field is populated
Monitoring Recommendations
- Enable WordPress audit logging to capture order state transitions and administrative configuration changes
- Forward WordPress and web server logs into a central analytics platform for correlation across stores
- Monitor fulfillment pipelines for shipments triggered by orders without matching blockchain settlement records
How to Mitigate CVE-2026-94299
Immediate Actions Required
- Configure a strong, non-empty shared secret in the elegro Crypto Payment plugin settings immediately
- Audit recent orders processed through the plugin for fraudulent status changes and reverse any that lack valid payment records
- Restrict access to the payment notification endpoint to the IP ranges used by the elegro gateway where feasible
Patch Information
As of the NVD publication on 2026-10-06, the vulnerability is reported in elegro Crypto Payment versions up to and including 1.0.1. Review the WPScan Vulnerability Report for the latest fixed version information and apply the vendor update when available.
Workarounds
- Set a strong shared secret in the plugin configuration to force signature validation on every callback
- Disable or uninstall the plugin until the shared secret is configured and the vendor confirms a fix
- Place the WordPress site behind a web application firewall and block callback requests that do not originate from the gateway's documented source addresses
# Configuration example: verify a non-empty shared secret is set
wp option get elegro_crypto_payment_settings --format=json | \
jq '.shared_secret | if . == "" or . == null then "VULNERABLE" else "OK" end'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

