Strategic Overview
- Status
- Unpatched
- Affected Plugin
- elegro Crypto Payment
- Affected Version
<= 1.0.1- CVSS
- 5.3Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-94299
At a glance
CVE-2026-94299 is a medium-severity Incorrect Authorization vulnerability in the elegro Crypto Payment WordPress plugin, affecting versions <= 1.0.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by JunHee CHO.
Vulnerability Overview
The elegro Crypto Payment plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.1. This is due to a missing capability check on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-863: Incorrect Authorization
Reaching this weakness in elegro Crypto Payment <= 1.0.1 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. No fixed build of this plugin is recorded for elegro Crypto Payment yet, so installs running <= 1.0.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C