dbcve.org
Wp Helper PremiumWordPress extension · Matbao

CVE-2024-9065

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to after 4.6.1 or later.
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
The WP Helper Premium plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'whp_smtp_send_mail_test' function in all versions up to, and including, 4.6.1. This makes it possible for unauthenticated attackers to send emails containing any content and originating from the vulnerable WordPress instance to any recipient. CVE-2025-24737 is likely a duplicate of this issue.

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 WP Helper Premium plugin for WordPress has a broken access control vulnerability in the 'whp_smtp_send_mail_test' function. This function lacks a capability check, allowing any unauthenticated user to abuse the plugin's SMTP mail functionality to send arbitrary emails from the compromised WordPress server to any recipient.

MitigationUpdate the WP Helper Premium plugin to version 4.6.2 or later which includes the missing capability check. If no patched version is available, disable the plugin immediately or block the vulnerable endpoint via WAF.

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 Helper PremiumWordPress extension
Affected:<= 4.6.1

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 if WP Helper Premium plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP Helper Premium' or 'Matbao Wp Helper Premium' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins and is activated.
  2. Identify the installed plugin version
    In the Plugins list page, click on the plugin name or view details to find the version number displayed alongside the plugin name.
    Affected if The installed version is 4.6.1 or lower.
  3. Verify the vulnerable function exists
    Access the WordPress site via FTP or file manager and locate the plugin directory (typically wp-content/plugins/wp-helper-premium or similar). Search the plugin files for the function named 'whp_smtp_send_mail_test'.
    Affected if The function 'whp_smtp_send_mail_test' is found in the plugin code without a capability check (such as current_user_can) preceding it.
  4. Confirm the AJAX or admin-ajax endpoint is accessible without authentication
    Check the plugin PHP files for the hook registration of the vulnerable function (commonly via add_action with 'wp_ajax_nopriv_whp_smtp_send_mail_test' or similar). This indicates the function can be called by unauthenticated users.
    Affected if The plugin registers the function with a nopriv hook or without requiring authentication.

If the WP Helper Premium plugin is installed with version 4.6.1 or lower and the whp_smtp_send_mail_test function is accessible to unauthenticated users, the environment is affected by CVE-2024-9065.

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 a release after 4.6.1
Interim mitigation

Update the WP Helper Premium plugin to version 4.6.2 or later which includes the missing capability check. If no patched version is available, disable the plugin immediately or block the vulnerable endpoint via WAF.

Recommended fix Moderate confidence

Version 4.6.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Helper Premium' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 4.6.2 or higher
  6. 6. Confirm the 'whp_smtp_send_mail_test' function now includes proper capability checks (e.g., current_user_can('manage_options'))

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

Fix this in Wp Helper Premium Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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