Web3 – Crypto wallet Login & NFT token gating <= 2.6.0 - Authentication Bypass
Strategic Overview
- Status
- Patched in 2.7.0
- Affected Plugin
- Web3 – Crypto wallet Login & NFT token gating
- Affected Version
<= 2.6.0- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2023-3249
At a glance
CVE-2023-3249 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Web3 WordPress plugin, affecting versions <= 2.6.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.7.0; sites on affected versions should update now. Disclosed June 2023, reported by István Márton.
Vulnerability Overview
The Web3 – Crypto wallet Login & NFT token gating plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.6.0. This is due to incorrect authentication checking in the 'hidden_form_data' function. This makes it possible for authenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Web3 <= 2.6.0 carries this weakness at hidden_form_data, and reaching it takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Web3 the fix is 2.7.0: builds <= 2.6.0 are affected, anything from 2.7.0 onward is not.
Remediation
Update to version 2.7.0, or a newer patched version
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. None of that substitutes for the fix: Web3 2.7.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C