dbcve.org
Wp MailsterWordPress extension · Wpmailster

CVE-2024-53805

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
Missing Authorization vulnerability in brandtoss WP Mailster wp-mailster allows Exploiting Incorrectly Configured Access Control Security Levels.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 · moderate confidence

This is a missing authorization (broken access control) vulnerability in the WP Mailster WordPress plugin. The vulnerability allows unauthenticated attackers to access functions or endpoints that should require proper authorization, likely due to missing capability checks or incorrect access control configurations. With a CVSS 9.8 rating, it is network-exploitable without authentication and could lead to unauthorized data access or configuration changes.

MitigationUpgrade WP Mailster to the latest version which should include proper authorization checks (capability verification) on sensitive functions and endpoints. If no patch is available, disable the plugin until a fix is released.

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. Locate the WP Mailster plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-mailster' or 'wpmailster'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to find WP Mailster in the list.
    Affected if The plugin folder exists in the plugins directory or the plugin appears in the WordPress admin plugins list.
  2. Identify the installed version number
    In the WordPress admin, find WP Mailster in the installed plugins list and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (usually wp-mailster.php or wpmailster.php) in the plugin folder and look for the 'Version' header in the plugin comment block.
    Affected if A version number is displayed or found in the plugin header.
  3. Compare version against the affected range
    Compare your identified version to 1.8.17. The affected range is any version less than 1.8.17.
    Affected if The installed version is 1.8.16, 1.8.15, or any version number lower than 1.8.17.
  4. Verify the vulnerability is exploitable
    Since this is a missing authorization flaw, confirm the plugin is active and accessible over the network (not behind IP restrictions). Check WordPress admin > Plugins to confirm WP Mailster status shows 'Active'.
    Affected if The plugin is active and the WordPress site is network-accessible.

You are affected if the WP Mailster plugin is installed, active, and running a version lower than 1.8.17.

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 which should include proper authorization checks (capability verification) on sensitive functions and endpoints. If no patch is available, disable the plugin until a fix is released.

Recommended fix High confidence

WP Mailster version 1.8.17

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP Mailster in the plugin list
  4. Check if the current version is below 1.8.17
  5. If vulnerable, click 'Update Now' on the WP Mailster plugin to update to version 1.8.17
  6. Alternatively, download version 1.8.17 from the official WordPress plugin repository and upload manually
  7. After updating, verify the new version number reflects 1.8.17 or higher
  8. Review plugin settings to ensure access control configurations are correct

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

Fix this in Wp Mailster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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