dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-0866

HIGH · 8.1 CVSS v3.1 Published 2024-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
The Check & Log Email plugin for WordPress is vulnerable to Unauthenticated Hook Injection in all versions up to, and including, 1.0.9 via the check_nonce function. This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress under certain circumstances. The action the attacker wishes to execute needs to have a nonce check, and the nonce needs to be known to the attacker. Furthermore, the absence of a capability check is a requirement.

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 · high confidence

The Check & Log Email WordPress plugin has an Unauthenticated Hook Injection vulnerability in the check_nonce function affecting versions up to 1.0.9. The flawed nonce validation allows unauthenticated attackers to execute WordPress hooks/actions if they know a valid nonce and the target action lacks a capability check.

MitigationUpdate the Check & Log Email plugin to version 1.0.10 or later. Until then, consider disabling the plugin or restricting access via web server authentication.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Locate the Check & Log Email plugin files
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'check-and-log-email' or similar
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (commonly check-and-log-email.php) and locate the version in the plugin header comment (e.g., 'Version: 1.0.x')
    Affected if The version read from the file is 1.0.9 or lower
  3. Confirm the plugin is active
    Query the WordPress database wp_options table where option_name='active_plugins', or use WP-CLI: wp plugin list --name='check-and-log-email' --status=active
    Affected if The plugin appears in the list of active plugins
  4. Verify the check_nonce function is in use
    Search the plugin source files for the function 'check_nonce' or 'wp_verify_nonce' to confirm the vulnerable code path exists
    Affected if The vulnerable nonce validation function is present in the plugin code

A user is affected if the Check & Log Email plugin is installed, active, and running version 1.0.9 or lower, with the flawed check_nonce function present in the codebase.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Check & Log Email plugin to version 1.0.10 or later. Until then, consider disabling the plugin or restricting access via web server authentication.

Recommended fix Moderate confidence

Check & Log Email version 1.1.0 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Check & Log Email' plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the fixed version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running on a version higher than 1.0.9

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

Have this fixed 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 help mitigating

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-2024-0866 — 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-2024-0866 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