Security readout for executives and security teams
Plain-English summary
A WordPress WooCommerce email-verification plugin can let an unauthenticated attacker become another user, including an administrator, when a non-default automatic-login setting is enabled. The business impact is potential full site takeover, customer data exposure, and fraudulent store changes on affected sites.
Executive priority
Treat this as high priority for any WooCommerce site using the plugin. The exposure condition is specific, but the worst-case impact is administrator account compromise and direct control of the store.
Technical view
CVE-2023-2781 affects User Email Verification for WooCommerce through version 3.5.0. Sources describe an authentication bypass involving authenticate_user_by_email and weak random token generation in resend_verification_email. Exploitation requires Allow Automatic Login After Successful Verification to be enabled, which sources say is not default.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites running this plugin at version 3.5.0 or earlier, especially where automatic login after successful verification is enabled. Sites without the plugin, or without that setting enabled, have materially lower exposure based on the provided description.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The issue is still serious because it is unauthenticated, network reachable on public WordPress sites, and can result in administrator impersonation when the required setting is enabled.
Researcher notes
The provided evidence identifies affected versions, root cause, privilege impact, CVSS 8.1, and the required non-default setting. It does not provide a specific patched version, proof of exploitation, or KEV status supporting active exploitation.
Mitigation direction
- Inventory WordPress sites for User Email Verification for WooCommerce version 3.5.0 or earlier.
- Disable Allow Automatic Login After Successful Verification where present.
- Check vendor, WordPress plugin, or Wordfence guidance for a named fixed version.
- Deactivate the plugin if a safe upgrade path cannot be confirmed.
- Review administrator accounts and recent unexpected account verification activity.
Validation and detection
- Confirm whether the plugin is installed and record its exact version.
- Check whether Allow Automatic Login After Successful Verification is enabled.
- Review authentication and account-verification logs for unexpected administrator sessions.
- Verify no new or modified administrator accounts were created unexpectedly.
- Confirm remediation against current vendor or plugin repository guidance.
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-2781 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
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/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:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/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/f1e31357-7fbc-414b-a4f4-53fa5f2fc715?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/woo-confirmation-email/tags/3.5.0/public/class-xlwuev-woocommerce-confirmation-email-public.php#L506CVE 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.