dbcve.org
Wp MailsterWordPress extension · Wpmailster

CVE-2024-54355

HIGH · 8.8 CVSS v3.1 Published 2024-12-16
Fix available
A fix is available. Upgrade to 1.8.17 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in brandtoss WP Mailster wp-mailster allows Cross Site Request Forgery.This issue affects WP Mailster: from n/a through <= 1.8.17.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

Cross-Site Request Forgery (CSRF) vulnerability in the WP Mailster WordPress plugin allows attackers to induce authenticated users to perform unintended state-changing actions. The lack of anti-CSRF tokens (nonces) on sensitive operations enables attackers to craft malicious requests that execute with the privileges of a logged-in user.

MitigationImplement WordPress nonces on all forms and AJAX endpoints that perform state-changing operations, and verify the nonce validation server-side before processing requests.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if WP Mailster plugin is installed
    Navigate to WordPress admin dashboard > Plugins page and locate 'WP Mailster' in the list of installed plugins, or check for the /wp-content/plugins/wp-mailster/ directory
    Affected if WP Mailster plugin exists in the WordPress installation
  2. Determine the installed WP Mailster version
    In WordPress admin > Plugins > Installed Plugins, click on WP Mailster to view the version number in the plugin details, or read the 'Version' header from the main plugin file (wp-mailster.php)
    Affected if Installed version is less than 1.8.17
  3. Review plugin code for nonce validation on sensitive operations
    Examine the plugin's PHP files that handle form submissions and AJAX endpoints. Search for missing wp_nonce_field() calls in forms and check_admin_referer() or wp_verify_nonce() calls before processing state-changing actions like subscriber management, list configuration, or email settings
    Affected if State-changing operations lack WordPress nonce verification and the installed version is below 1.8.17

The environment is affected if WP Mailster plugin version is below 1.8.17 and the plugin processes sensitive actions without validating anti-CSRF nonces

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

Implement WordPress nonces on all forms and AJAX endpoints that perform state-changing operations, and verify the nonce validation server-side before processing requests.

Recommended fix High confidence

WP Mailster 1.8.18

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find WP Mailster in the list of installed plugins
  5. 5. If an update is available, click 'Update Now' to update to the latest version (1.8.18)
  6. 6. Alternatively, download WP Mailster 1.8.18 from the official WordPress plugin repository
  7. 7. Deactivate the current plugin, delete it, then upload and install version 1.8.18
  8. 8. After update, verify the plugin is functioning correctly by testing email forwarding features
Caveat Review plugin settings after upgrade as minor configuration adjustments may be needed

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-54355 — 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-54355 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