dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-53732

HIGH · 7.1 CVSS v3.1 Published 2024-11-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in wpwox Footer Flyout Widget footer-flyout-widget allows Stored XSS.This issue affects Footer Flyout Widget: from n/a through <= 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 confidence

This is a CSRF-to-Stored XSS vulnerability in the Footer Flyout Widget WordPress plugin. Attackers can exploit CSRF to trick authenticated administrators into submitting malicious requests that store XSS payloads in the widget settings. Once stored, the XSS executes whenever users view pages containing the footer flyout widget.

MitigationImplement WordPress nonces on all form submissions and AJAX handlers in the plugin, validate and sanitize all user inputs before storage, and escape output when rendering the widget 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Footer Flyout Widget plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Footer Flyout Widget' or check the plugins directory via file system for /wp-content/plugins/footer-flyout-widget/
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin_plugins list, find the Footer Flyout Widget entry and note the version number displayed under the plugin name. Compare this version to any official changelog or security advisory if available.
    Affected if Version is unknown or falls within any affected range (no specific range provided in CVE data)
  3. Inspect widget settings for stored XSS payloads
    Navigate to Appearance > Widgets (or the plugin settings page if it has a dedicated settings screen). Locate any Footer Flyout Widget instances and examine all text fields (title, content, links, etc.) for unexpected HTML script tags, javascript: URIs, or event handler attributes like onload, onerror, onclick.
    Affected if Any widget setting contains raw script tags, javascript: protocols, or suspicious event handlers (onload, onerror, onmouseover, etc.)
  4. View page source for injected scripts
    Visit a page where the footer flyout widget is displayed, right-click and view page source, then search for script tags or inline JavaScript that does not belong to the site. Check for eval(), document.write(), or suspicious string references in the widget output area.
    Affected if The rendered page contains unexpected script injections originating from widget settings
  5. Check WordPress admin for unauthorized changes
    Review recent activity in the plugin settings or widget areas. Look for changes made by users who should not have admin access, or verify that all settings were intentionally configured by legitimate administrators.
    Affected if Widget settings were modified without legitimate admin action or contain content you did not add

You are affected if the Footer Flyout Widget plugin is installed AND its settings contain unexpected HTML script tags, javascript: URIs, or event handler attributes, indicating a stored XSS payload was injected via CSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces on all form submissions and AJAX handlers in the plugin, validate and sanitize all user inputs before storage, and escape output when rendering the widget content.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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