CVE-2024-54388
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 Phuc Pham Multiple Admin Emails multiple-admin-emails allows Cross Site Request Forgery.This issue affects Multiple Admin Emails: from n/a through <= 1.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Multiple Admin Emails WordPress plugin by Phuc Pham allows attackers to trick authenticated administrators into performing unintended actions, such as modifying admin email configurations. The plugin lacks proper anti-CSRF token validation (nonce verification) on state-changing operations.
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 plugin installationNavigate to WordPress admin > Plugins and check if 'Multiple Admin Emails' by Phuc Pham is installed and activeAffected if Plugin is installed and active
-
Check installed versionIn Plugins list, view the version column for Multiple Admin Emails or check the plugin header in its main PHP file (wp-content/plugins/multiple-admin-emails/multiple-admin-emails.php)Affected if Installed version matches or falls within the affected version range (compare to known vulnerable versions)
-
Identify state-changing functionsReview plugin PHP files for functions that modify settings: email configuration updates, admin email additions/deletions, or options saves. Look for form handlers and AJAX action callbacksAffected if Plugin contains functions that modify admin email configurations
-
Inspect nonce validationExamine the identified state-changing functions for nonce verification code. Search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' calls within these functionsAffected if State-changing functions lack nonce verification or have insufficient CSRF protection
-
Verify form nonce fieldsCheck plugin templates/forms for nonce field generation using 'wp_nonce_field' or 'wp_nonce_url' on forms that submit state-changing requestsAffected if Forms modifying email settings are missing nonce field outputs
If the Multiple Admin Emails plugin is installed and its state-changing operations lack proper nonce validation, the environment is vulnerable to CVE-2024-54388 CSRF attacks.
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 nonces and proper CSRF token validation on all form submissions and AJAX actions within the plugin; add origin/referer header checks to verify request legitimacy.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54388 — 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-54388 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