User Email Verification For WoocommerceWordPress extension · Wisetr
CVE-2018-21007
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe woo-confirmation-email plugin before 3.2.0 for WordPress has no blocking of direct access to supportive xl folders inside uploads.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe woo-confirmation-email plugin before version 3.2.0 lacks proper access controls, allowing unauthenticated direct access to supportive XL folders within the WordPress uploads directory. This exposes sensitive files or data that should be protected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
User Email Verification For WoocommerceWordPress extension
< 3.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'woo-confirmation-email' or search for 'Wisetr User Email Verification For Woocommerce' in the WordPress admin plugins listAffected if The plugin folder 'woo-confirmation-email' or 'wise-woocommerce-email-verification' exists in the plugins directory
-
Check the installed plugin versionIf the plugin is installed, open the main plugin file (usuallywoo-confirmation-email.php or similar) and look for the 'Version' header in the plugin comments, or check the version in the WordPress admin plugins listAffected if The reported version number is less than 3.2.0 (for example, 3.1.0, 3.0.0, etc.)
-
Locate the uploads directory and XL foldersBrowse to wp-content/uploads/ and look for any subdirectories named 'xl', 'xl_files', or similar supportive folders created by the plugin. These may be within a 'woo-confirmation-email' subfolderAffected if XL or supportive folders exist within the uploads directory and are directly accessible via URL
-
Test direct access to sensitive foldersAttempt to access the suspected XL folder directly via a web browser (for example, yoursite.com/wp-content/uploads/woo-confirmation-email/xl/ or similar path). If the server returns a file listing or allows downloading files without authentication, the vulnerability is presentAffected if Direct HTTP access to the folder returns a directory listing or exposes files without requiring authentication or login
You are affected if the Wisetr User Email Verification For Woocommerce plugin is installed with a version lower than 3.2.0 AND the XL folders in the uploads directory are directly accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.2.0
Update the plugin to version 3.2.0 or later, which implements proper access restrictions. Alternatively, add .htaccess rules or index.php files to block direct access to sensitive directories.
3.2.0
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'User Email Verification For WooCommerce' (also known as woo-confirmation-email) plugin
- Check if version 3.2.0 or later is available as an update
- Click 'Update Now' to install the latest version
- After update completes, verify the plugin version is 3.2.0 or higher under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in User Email Verification For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-21007 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data