CVE-2024-54431
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 phpdevp Admin Customization wpp-customization allows Stored XSS.This issue affects Admin Customization: from n/a through <= 2.2.
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 phpdevp Admin Customization plugin (wpp-customization) allows attackers to inject malicious scripts that persist in the application's storage (Stored XSS). By tricking authenticated administrators into visiting attacker-controlled pages, the CSRF flaw enables the injection of malicious JavaScript that executes whenever other users access the affected admin interface areas.
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.
-
Identify if wpp-customization plugin is installedCheck your WordPress site's plugin directory or admin panel for the 'phpdevp Admin Customization' or 'wpp-customization' plugin. Look for files named 'wpp-customization' or similar in /wp-content/plugins/Affected if The plugin is installed and active on the WordPress site
-
Verify admin actions lack CSRF protectionExamine the plugin's PHP files for form submissions and state-changing admin actions. Search for missing 'nonce' verification or 'check_admin_referer' calls in functions handling POST/GET requests that modify settingsAffected if Admin actions that change settings or data do not validate CSRF tokens (nonces)
-
Test for stored XSS injection pointsAccess admin interface areas provided by the plugin (typically in wp-admin under the plugin menu). Submit HTML or JavaScript payloads in input fields such as custom scripts, headers, footers, or branding options, then verify if the input is stored and reflected back unescapedAffected if User-supplied input in admin settings is stored and rendered without proper HTML encoding or sanitization
You are affected if the wpp-customization plugin is active AND its admin actions lack CSRF token validation AND input fields in the plugin settings accept and reflect back unescaped HTML/JavaScript.
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 on all state-changing admin actions and apply proper input validation with context-aware output encoding to prevent the stored XSS. Users should avoid clicking untrusted links while authenticated until a vendor patch is available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54431 — 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-54431 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