{"id":"CVE-2026-94299","title":"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 chan…","summary":"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 chan…","severity":"none","cwe":["CWE-863"],"product":"elegro Crypto Payment","affected":["elegro_crypto_payment <= 1.0.1"],"published":"2026-10-06","updated":"2026-10-06","sourceUpdated":"2026-10-06T07:17:00.360","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-94299","references":[{"url":"https://wpscan.com/vulnerability/7eb85c65-8dab-46e1-b1df-e5d966029b18/","label":"contact@wpscan.com"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-10-06T06:48:36.103Z","slug":"CVE-2026-94299","body":"## Overview\n\nThe 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}