CVE-2024-54394
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in khubbaib Mandrill WP email-form-under-post allows Stored XSS.This issue affects Mandrill WP: from n/a through <= 1.0.5.
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 confidenceA CSRF vulnerability in the Mandrill WP WordPress plugin (versions up to 1.0.5) allows authenticated administrators to be tricked into submitting malicious requests that inject Stored XSS payloads into the application. Since the XSS is stored, it executes whenever admins or users view affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Mandrill WP plugin is installedGo to WordPress admin > Plugins and look for 'Mandrill WP' or check the plugins directory for /wp-content/plugins/mandrill-wp/Affected if The plugin is installed and active
-
Check installed plugin versionIn WordPress admin > Plugins, find Mandrill WP and note the version number displayedAffected if Version is 1.0.5 or lower
-
Inspect plugin admin forms for CSRF protectionView the plugin admin pages (typically under Settings > Mandrill or similar), view page source, and search for wp_nonce_field or nonce tokens in all form tagsAffected if Forms lack nonce/token fields or the nonce verification is missing from form handling code
-
Check database for stored XSS in plugin settingsQuery wp_options table for mandrill-related entries: SELECT * FROM wp_options WHERE option_name LIKE '%mandrill%'; Examine stored values for script tags, iframe tags, or event handlers (onerror, onload, etc.)Affected if Stored values contain unescaped HTML/JavaScript payloads
-
Review plugin output for unescaped dataExamine plugin PHP files for functions that output stored data without using esc_html(), esc_attr(), or similar WordPress escaping functionsAffected if User-supplied data is output without proper escaping
You are affected if the Mandrill WP plugin version is 1.0.5 or lower AND admin forms lack CSRF protection OR stored XSS payloads are present in the database.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all form submissions and admin actions, and ensure all user inputs are properly sanitized before storage and escaped before output to prevent XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-54394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54394 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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