CVE-2026-94299

elegro Crypto Payment <= 1.0.1 - Unauthenticated Arbitrary Order Status Change via IPN Callback

Published Oct 6, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
The elegro Crypto Payment WordPress plugin through 1.0.1 does not require a shared secret to be configured before trusting incoming payment notification requests, allowing unauthenticated attackers to forge payment confirmations and change the status of arbitrary orders on any installation where that secret has been left at its default empty value.

Analysis

AI-generated

Technical impact

The elegro Crypto Payment WordPress plugin, in all releases up to version 1.0.1, fails to enforce a shared secret when processing inbound payment notification requests. This omission allows an attacker that does not possess any authentic credentials to forge an IPN callback and modify the status of any order on a target site. The flaw is a classic example of improper authorization and can be used to arbitrarily cancel orders, mark payments as complete, or otherwise manipulate transaction data, resulting in financial fraud or revenue loss.

Affected Systems

WordPress installations that have installed the elegro Crypto Payment plugin version 1.0.1 or earlier and have left the shared‑secret configuration field empty are affected. No Common Platform Enumeration strings are supplied in the CVE data.

Risk and Exploitability

The CVSS score is 6.5 and the EPSS score is <1%, but the vulnerability permits direct manipulation of order status without any authentication, indicating a moderate‑severity risk. The exploitation path consists of a simple forged HTTP to the plugin’s IPN callback endpoint; no prior credentials or privileged access are required. Because the flaw is entirely driven by external input, the likelihood of exploitation is substantial for sites still using the default empty secret configuration. The vulnerability is not listed in the CISA KEV catalog at this time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade elegro Crypto Payment to the latest release where shared‑secret verification is enforced.
  • If an upgrade is not feasible, configure a non‑empty shared secret and modify the plugin (or use a plugin hook) to validate the secret before processing any IPN request.
  • Restrict the visibility of the IPN handler to the payment provider’s IP addresses or add an additional token check to ensure only legitimate callbacks are processed.

Generated by OpenCVE AI on October 7, 2026 at 06:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions elegro Crypto Payment
Vendors & Products Wordpress-extensions
Wordpress-extensions elegro Crypto Payment
Type Values Removed Values Added
Weaknesses CWE-863
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-20
CWE-285
Type Values Removed Values Added
Description The elegro Crypto Payment WordPress plugin through 1.0.1 does not require a shared secret to be configured before trusting incoming payment notification requests, allowing unauthenticated attackers to forge payment confirmations and change the status of arbitrary orders on any installation where that secret has been left at its default empty value.
Title elegro Crypto Payment <= 1.0.1 - Unauthenticated Arbitrary Order Status Change via IPN Callback
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 6, 2026, 10:41 AM
Reserved
Sep 21, 2026, 9:45 AM
Status
Deferred
Published
Oct 6, 2026, 7:17 AM
Modified
Oct 6, 2026, 3:18 PM