Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw could let an attacker sign in as another site user, including an administrator, if the vulnerable Web3 login plugin is present. For an exposed WordPress site, the business impact is potential full site takeover, content tampering, data access, and loss of administrative control.
Executive priority
Treat as urgent for any WordPress site using this plugin, especially public sites or revenue-critical properties. The potential impact is administrator compromise. Prioritize inventory, update or disablement, and post-remediation review of privileged activity.
Technical view
CVE-2023-3249 affects Web3 – Crypto wallet Login & NFT token gating up to and including 2.6.0. The source bundle attributes the issue to incorrect authentication checking in the hidden_form_data function. CVSS 3.1 is 9.8 with network access, low complexity, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites running the cyberlord92 Web3 – Crypto wallet Login & NFT token gating plugin at version 2.6.0 or earlier. Sites without this plugin, or with a fixed newer version, are not indicated as affected by the provided sources.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. It reports authentication bypass risk and says attackers may log in as existing users if they know a username. One source detail is inconsistent: the description says authenticated attackers, while the CVSS vector lists privileges required as none.
Researcher notes
The provided references identify the vulnerable function and a WordPress repository changeset. Do not assume active exploitation from the bundle. The authenticated-versus-unauthenticated wording conflict should be resolved against vendor and NVD/Wordfence records during case handling.
Mitigation direction
- Inventory WordPress sites for the affected plugin and version.
- Update the plugin to a vendor-supported version newer than 2.6.0, if available.
- If update is unavailable, disable or remove the plugin until vendor guidance is confirmed.
- Review privileged WordPress accounts for unexpected changes or sessions.
- Check Wordfence and WordPress plugin repository guidance for fixed release details.
Validation and detection
- Confirm no production site runs plugin version 2.6.0 or earlier.
- Verify the plugin update includes the referenced WordPress changeset fix.
- Review administrator login history for unusual access after the disclosure date.
- Check for unexpected new users, role changes, or content modifications.
- Confirm web application monitoring covers WordPress authentication anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-3249 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e30b62de-7280-4c29-b882-dfa83e65966b?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/web3-authentication/tags/2.6.0/classes/common/Web3/controller/class-moweb3flowhandler.php#L198CVE reference
- https://plugins.trac.wordpress.org/changeset/2933325/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.