dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67578

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Rhys Wynne WP Email Capture wp-email-capture allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Email Capture: from n/a through <= 3.12.4.

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

The WP Email Capture WordPress plugin (versions up to 3.12.4) contains a missing authorization vulnerability where certain administrative or sensitive functions lack proper access control checks. This allows unauthenticated or lower-privileged users to access functionality that should be restricted to higher-privilege users, due to incorrectly configured access control security levels.

MitigationUpdate WP Email Capture to the latest patched version once available. Until then, review user role capabilities and restrict access to plugin settings via WordPress access controls, or disable the plugin if the vulnerable functionality is not essential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Check installed WP Email Capture version
    In WordPress admin, go to Plugins > Installed Plugins > WP Email Capture. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (typically wp-email-capture.php) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is 3.12.4 or any earlier version (e.g., 3.12.3, 3.12.0, 3.10, etc.).
  2. Verify plugin is active
    Confirm WP Email Capture is currently activated in the WordPress plugins admin panel. The vulnerability only applies when the plugin is actively loaded.
    Affected if The plugin shows as 'Active' in the WordPress admin plugins list.
  3. Identify administrative or sensitive plugin functions
    Inspect the plugin directory (typically /wp-content/plugins/wp-email-capture/) for PHP files containing admin-related functions, AJAX handlers, or settings pages. Look for functions that modify plugin settings, manage email lists, or interact with WordPress options. Common indicators include: add_action calls with 'admin_', 'wp_ajax_', or settings-related hooks.
    Affected if The plugin directory contains administrative functions, AJAX endpoints, or settings handlers that handle sensitive operations (such as saving options, importing/exporting data, or modifying user lists).
  4. Test access control on sensitive plugin endpoints
    Attempt to access identified admin functions or AJAX endpoints while logged in as a low-privilege user (e.g., Subscriber role) or while logged out (unauthenticated). In WordPress, this can be done by sending direct requests to admin-ajax.php?action=wp_email_capture_* or visiting plugin admin pages directly with a limited user account.
    Affected if Requests to administrative functions return successful responses (HTTP 200) without requiring admin-level privileges, indicating missing capability checks.
  5. Review WordPress user roles and plugin capability requirements
    Check the plugin code for calls to current_user_can(), admin_menu, or add_submenu_page to determine what capability level the plugin claims to require. Compare this against actual enforcement by inspecting the function callbacks for the identified sensitive operations.
    Affected if The plugin defines high-level capabilities (like 'manage_options') in menu registrations but fails to enforce these checks inside the actual function logic, allowing lower-privileged users to execute restricted actions.

A user is affected if WP Email Capture plugin version 3.12.4 or lower is active AND sensitive administrative functions are accessible to unauthenticated or low-privileged users due to missing capability checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Email Capture to the latest patched version once available. Until then, review user role capabilities and restrict access to plugin settings via WordPress access controls, or disable the plugin if the vulnerable functionality is not essential.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67578 — 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-2025-67578 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