CVE-2024-54401
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 Ciprian Turcu Advanced Fancybox advanced-fancybox allows Stored XSS.This issue affects Advanced Fancybox: from n/a through <= 1.1.1.
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 · high confidenceA CSRF vulnerability in Advanced Fancybox plugin versions <=1.1.1 allows attackers to trick authenticated administrators into performing unintended actions that inject malicious JavaScript, resulting in stored XSS. Attackers exploit the lack of anti-CSRF tokens in admin forms to embed XSS payloads that persist for all users viewing the affected content.
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 Advanced Fancybox plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Locate 'Advanced Fancybox' or similar fancybox plugin in the list.Affected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the plugins list, view the plugin details or version information for Advanced Fancybox. Compare the version number to 1.1.1.Affected if The installed version is 1.1.1 or any earlier version
-
Inspect admin forms for CSRF protectionAccess plugin settings pages in the WordPress admin panel. View the HTML source code of any forms that perform state-changing actions (settings saves, configuration changes). Look for input fields containing 'nonce' or 'CSRF' tokens.Affected if No nonce or CSRF token fields are present in admin forms that modify plugin settings
-
Verify nonce validation on form submissionsExamine the plugin PHP files handling form submissions (typically in the main plugin file or admin class). Search for calls to 'check_admin_referer', 'wp_verify_nonce', or similar nonce verification functions.Affected if Form handling code lacks nonce verification calls before processing submissions
-
Test for stored XSS vulnerabilitySubmit a test XSS payload (such as <script>alert('XSS')</script>) in plugin admin input fields. Save the settings and then view the affected page or frontend area where the content is displayed.Affected if The submitted JavaScript executes or renders unescaped when viewing the affected content
The environment is affected if Advanced Fancybox plugin version 1.1.1 or earlier is installed AND admin forms lack CSRF nonce validation, allowing stored XSS injection.
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 plugin version if available; otherwise add anti-CSRF nonce validation to all state-changing admin actions and implement proper input sanitization to prevent stored XSS.
- Consultation2.0 h
- Implementation5.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54401 — 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-54401 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