CVE-2024-54411
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 hosting.io WP Controller wp-management-controller allows Stored XSS.This issue affects WP Controller: from n/a through <= 3.2.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 confidenceA CSRF vulnerability in the WP Controller plugin allows authenticated administrators to be tricked into submitting requests that inject stored XSS payloads. The flaw exists in the wp-management-controller component, where state-changing operations lack proper anti-CSRF tokens, enabling persistent JavaScript execution in the admin dashboard.
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 WP Controller plugin is installedNavigate to Plugins > Installed Plugins in WordPress admin and look for 'WP Controller' in the list. Check if it shows as Active.Affected if The WP Controller plugin is installed and active in WordPress.
-
Check installed WP Controller versionClick the plugin name or view the plugin details to see the installed version number. Compare this to the latest version available from the WordPress plugin repository or the vendor.Affected if The installed version is older than the patched version (if known) or remains vulnerable.
-
Identify wp-management-controller componentInspect the plugin files via FTP or file manager. Look for a file or directory named 'wp-management-controller' or containing 'controller' in the wp-content/plugins/wp-controller path.Affected if The wp-management-controller component exists and handles admin form submissions.
-
Inspect forms for CSRF token presenceView page source of admin pages created by WP Controller. Look at form tags and AJAX requests for an input field or header containing a CSRF token (commonly named 'nonce', '_wpnonce', 'csrf_token', or similar).Affected if Forms handling state-changing operations (add/edit/delete) lack CSRF token validation.
-
Check for existing stored XSS in databaseReview database tables where WP Controller stores user data (look for tables with 'controller', 'wp_controller', or custom post types). Inspect stored values for unsanitized script tags, img onerror attributes, or JavaScript event handlers.Affected if Malicious stored XSS payloads already exist in the database, indicating exploitation.
If WP Controller is active, the installed version lacks CSRF protection in the wp-management-controller component, and state-changing forms do not use anti-CSRF tokens, the environment is vulnerable to CVE-2024-54411.
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 dataUpdate to the latest version of WP Controller if available, or disable the plugin until a patch is released. Implement anti-CSRF tokens on all form submissions and AJAX requests, and ensure all user-supplied data is properly sanitized before storage and output.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54411 — 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-54411 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