CVE-2024-54433
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 Marcel CL Simple Booking Widget simple-booking-widget allows Stored XSS.This issue affects Simple Booking 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 confidenceA CSRF vulnerability in the Marcel CL Simple Booking Widget plugin allows authenticated administrators to be tricked into storing malicious JavaScript payloads via crafted requests. Since the widget lacks anti-CSRF tokens on its admin forms, an attacker can embed XSS scripts that persist in booking data and execute when other users view the booking widget.
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.
-
Confirm plugin is installedCheck your WordPress plugins directory or admin panel for 'Marcel CL Simple Booking Widget'Affected if The plugin is present in the WordPress installation
-
Identify installed versionLook in the plugin header (usually in main PHP file) or WordPress plugin admin page for the version numberAffected if Version is present and matches any known affected versions of this plugin
-
Inspect admin form source for nonce tokensView the source HTML of the plugin admin configuration pages and search for wp_nonce_field or similar nonce-related input fieldsAffected if No nonce or CSRF token fields are found in the admin forms for the booking widget settings
-
Check form submission handlingExamine the PHP file handling admin form submissions for presence of check_admin_referer or wp_verify_nonce callsAffected if No nonce verification is performed when processing admin configuration submissions
-
Review booking data storage for sanitizationExamine the code that saves booking data to the database and look for sanitization functions like sanitize_text_field, esc_html, or esc_attrAffected if Booking data is stored without proper input sanitization functions
-
Check output encoding when displaying bookingsInspect the code that renders the booking widget on the frontend for context-aware output encoding functionsAffected if Booking data is output without esc_html, esc_attr, or similar encoding when displayed in the widget
If the Marcel CL Simple Booking Widget plugin is installed and its admin forms lack CSRF nonce validation, the environment is affected by this vulnerability.
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 (nonce validation) on all admin configuration forms and apply proper input sanitization plus context-aware output encoding when displaying booking data to prevent stored XSS.
- 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-54433 — 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-54433 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