dbcve.org
Wp MailsterWordPress extension · Wpmailster

CVE-2024-53807

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-06
Fix available
A fix is available. Upgrade to 1.8.17 or later.
See remediation →
100/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in brandtoss WP Mailster wp-mailster allows Blind SQL Injection.This issue affects WP Mailster: from n/a through <= 1.8.16.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

A blind SQL injection vulnerability exists in WP Mailster WordPress plugin versions through 1.8.16.0. The vulnerability allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or privilege escalation. As a blind SQL injection, attackers infer information from application behavior differences rather than direct error output.

MitigationUpgrade WP Mailster to the latest version if a patch is available. If no patched version exists, implement immediate input validation and convert vulnerable database queries to use parameterized queries or prepared statements.

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 MailsterWordPress extension
Affected:< 1.8.17

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Verify WP Mailster plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the wp-mailster folder
    Affected if The WP Mailster plugin folder exists in the WordPress installation
  2. Check WP Mailster plugin version
    In WordPress admin, find WP Mailster in the plugins list and view the version number displayed, or read the main plugin file (e.g., wp-mailster.php) and locate the 'Version' header comment
    Affected if The installed version is lower than 1.8.17 (e.g., 1.8.16, 1.8.0, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the WP Mailster plugin shows as 'Active'
    Affected if The plugin is active and therefore accessible to unauthenticated attackers

A WordPress site is affected if it has WP Mailster plugin installed with a version prior to 1.8.17 and the plugin is active, exposing the unsanitized input parameters to potential blind SQL injection attacks.

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

Upgrade WP Mailster to the latest version if a patch is available. If no patched version exists, implement immediate input validation and convert vulnerable database queries to use parameterized queries or prepared statements.

Recommended fix High confidence

WP Mailster 1.8.17

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find WP Mailster in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.8.17.
  6. 6. Alternatively, download WP Mailster 1.8.17 from the official WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins.
  8. 8. Test that the plugin functions correctly, particularly any email forwarding or mailing features.

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

Fix this in Wp Mailster Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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