dbcve.org
NewsletterWordPress extension

CVE-2024-5674

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to 2.4.6 or later.
See remediation →
74/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
The Newsletter - API v1 and v2 addon plugin for WordPress is vulnerable to unauthorized subscribers management due to PHP type juggling issue on the check_api_key function in all versions up to, and including, 2.4.5. This makes it possible for unauthenticated attackers to list, create or delete newsletter subscribers. This issue affects only sites running the PHP version below 8.0

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 Newsletter plugin for WordPress contains a PHP type juggling vulnerability in its check_api_key function within the API v1/v2 addon. This flaw allows unauthenticated attackers to bypass authentication through the API by exploiting how PHP handles type comparisons when checking API keys. The vulnerability is exploitable only on PHP versions below 8.0, and enables attackers to list, create, or delete newsletter subscribers.

MitigationUpgrade the Newsletter plugin to version 2.4.6 or higher, and/or upgrade PHP to version 8.0 or later to eliminate the type juggling attack surface.

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
NewsletterWordPress extension
Affected:< 2.4.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Newsletter plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate the Newsletter plugin. The version is displayed in the plugin description. Alternatively, inspect the main plugin file (newsletter.php) and look for the 'Version' header comment.
    Affected if The installed version is lower than 2.4.6
  2. Check PHP version
    Run `php -v` from command line, or create a PHP file containing `<?php echo phpversion(); ?>` and access it via web browser, or check through hosting control panel.
    Affected if PHP version is below 8.0 (e.g., 7.4, 7.3, etc.)
  3. Verify API v1/v2 addon is active
    Log into WordPress Admin, go to Newsletter plugin settings, and check if the API addon (API v1 or API v2) is enabled under the Addons or API configuration section.
    Affected if The API v1 or API v2 addon is enabled and accessible
  4. Confirm API endpoint accessibility
    Attempt to access the API endpoint directly (commonly at /?newsletter_api=1 or /wp-json/newsletter/v1/) using a tool like curl or browser developer tools to see if authentication can be bypassed.
    Affected if The API endpoint responds without requiring valid authentication

The environment is affected if the Newsletter plugin version is below 2.4.6, PHP version is below 8.0, and the API v1/v2 addon is enabled, allowing unauthenticated API access.

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 2.4.6 or later
Fixed in 2.4.6
Interim mitigation

Upgrade the Newsletter plugin to version 2.4.6 or higher, and/or upgrade PHP to version 8.0 or later to eliminate the type juggling attack surface.

Recommended fix High confidence

Newsletter plugin version 2.4.6

  1. Backup the WordPress site database and files before updating
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate the Newsletter plugin in the installed plugins list
  4. Click 'Update now' when version 2.4.6 is available, or manually upload version 2.4.6 from wordpress.org/plugins
  5. Verify the plugin version shows 2.4.6 or later after update
  6. Test newsletter subscriber creation and management to confirm functionality works
Caveat Standard minor version security patch - minimal risk; test in staging if possible but should be compatible with existing configurations

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

Fix this in Newsletter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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