Code InjectionWeakness · CWE-94

CVE-2024-0867

HIGH · 8.1 CVSS v3.1 Published 2024-05-24
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 Email Log plugin for WordPress is vulnerable to Unauthenticated Hook Injection in all versions up to, and including, 2.4.8 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 Email Log WordPress plugin (versions up to 2.4.8) contains a vulnerability in its check_nonce function that allows unauthenticated attackers to bypass nonce validation under specific conditions. Attackers can execute WordPress hooks that have nonce checks (with known nonce values) but lack capability checks, allowing unauthorized actions on the site.

MitigationUpdate the Email Log plugin to version 2.4.9 or later immediately. Given the CVSS 8.1 score and unauthenticated attack vector, prioritize patching or disable the plugin until the update can be applied.

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. Confirm Email Log plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Email Log' in the list of active plugins, or check the file /wp-content/plugins/email-log/email-log.php for the version declaration.
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version number
    In WordPress admin Plugins page, click on the Email Log plugin to view its details, or open /wp-content/plugins/email-log/readme.txt and locate the 'Stable tag' entry in the file header.
    Affected if The version is 2.4.8 or lower, or the version cannot be determined (treat as vulnerable)
  3. Verify the nonce check vulnerability condition
    The vulnerability exists in the check_nonce function within the plugin. If running a vulnerable version, any WordPress hook that performs nonce validation but lacks capability checks can be triggered by unauthenticated attackers with known nonce values.
    Affected if Plugin version is 2.4.8 or lower AND the site has any WordPress hooks that use nonce checks without capability validation

The environment is affected if the Email Log plugin is installed with any version up to and including 2.4.8, as unauthenticated attackers can bypass nonce validation to execute certain WordPress hooks.

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 Email Log plugin to version 2.4.9 or later immediately. Given the CVSS 8.1 score and unauthenticated attack vector, prioritize patching or disable the plugin until the update can be applied.

Recommended fix Moderate confidence

Email Log plugin version 2.4.9 or latest available

  1. Check current Email Log plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload or update directly via Plugins > Add New
  3. Update to the latest version of the Email Log plugin (version 2.4.9 or later)
  4. Verify the update was successful by confirming the new version number

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0867 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0867 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