dbcve.org
Wp Email CaptureWordPress extension · Winwar

CVE-2023-23724

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 3.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Winwar Media WP Email Capture plugin <= 3.9.3 versions.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Email Capture WordPress plugin versions 3.9.3 and below allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings, creating email capture forms, or exfiltrating subscriber data.

MitigationImplement WordPress nonces on all plugin forms, AJAX calls, and administrative actions to verify request authenticity and prevent CSRF attacks.

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
Wp Email CaptureWordPress extension
Affected:< 3.10

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP Email Capture plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Email Capture' by Winwar. Alternatively, check the /wp-content/plugins/ directory for the wp-email-capture folder.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WP Email Capture, and note the version number displayed. Compare against the affected range: versions below 3.10 (including 3.9.3 and earlier).
    Affected if Version shown is below 3.10 (e.g., 3.9.3, 3.9.2, etc.)
  3. Inspect plugin settings forms for nonce fields
    Navigate to the plugin settings pages (WP Email Capture > Settings, WP Email Capture > Forms). View the page source (right-click > View Page Source) and search for 'wp_create_nonce' or '_wpnonce' within the <form> tags on those pages.
    Affected if Forms lack nonce fields (no _wpnonce or wp_create_nonce calls found in the form markup)
  4. Check plugin AJAX handlers for nonce verification
    Examine the plugin files in /wp-content/plugins/wp-email-capture/includes/ for AJAX action handlers. Look for calls to wp_verify_nonce or check_admin_referer within functions handling form submissions or settings changes.
    Affected if AJAX handlers do not verify nonces (no wp_verify_nonce or check_admin_referer calls present)

If the plugin is installed with a version below 3.10 AND the plugin forms/handlers lack nonce verification, the environment is vulnerable to CVE-2023-23724 CSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.10 or later
Fixed in 3.10
Interim mitigation

Implement WordPress nonces on all plugin forms, AJAX calls, and administrative actions to verify request authenticity and prevent CSRF attacks.

Recommended fix High confidence

WP Email Capture version 3.10 or later

  1. Backup the WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate WP Email Capture plugin
  4. Click 'Update now' to update to the latest version (3.10 or later), or use wp-cli: wp plugin update wp-email-capture
  5. Verify the plugin version after update to confirm the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Email Capture Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23724 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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