dbcve.org
Restaurant \& Cafe Addon For ElementorWordPress extension · Nicheaddons

CVE-2024-54316

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 1.5.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in nicheaddons Restaurant & Cafe Addon for Elementor restaurant-cafe-addon-for-elementor allows DOM-Based XSS.This issue affects Restaurant & Cafe Addon for Elementor: from n/a through <= 1.5.8.

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

DOM-based Cross-site Scripting (XSS) vulnerability in the Restaurant & Cafe Addon for Elementor plugin. The vulnerability allows attackers to inject malicious JavaScript through unsanitized user input that is dynamically rendered in the page's DOM without proper output encoding.

MitigationUpdate the plugin to version 1.5.9 or later which contains the security fix. If unable to update immediately, disable the affected plugin or implement WAF rules to block XSS attack patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Restaurant \& Cafe Addon For ElementorWordPress extension
Affected:< 1.5.9

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Check if Nicheaddons Restaurant & Cafe Addon is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Nicheaddons Restaurant & Cafe Addon For Elementor' in the list. Alternatively, check the wp-content/plugins directory for a folder named similarly to 'nicheaddons' or containing 'restaurant' or 'cafe'.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin name to view its details, or check the plugin's main PHP file for a 'Version' header in the plugin comment block.
    Affected if The version number cannot be determined or is displayed
  3. Compare the version against the affected range
    If version is found, compare it to the affected range: versions less than 1.5.9 are vulnerable. For example, 1.5.8, 1.5.7, 1.0.0 would be affected; 1.5.9 or later would not be.
    Affected if The installed version is lower than 1.5.9 (e.g., 1.5.8, 1.5.7, 1.0.1, etc.)
  4. Identify if Elementor page builder is active
    Check if Elementor page builder is installed and active on the WordPress site, as this addon requires Elementor to function.
    Affected if Elementor is active and the vulnerable plugin version is installed

A user is affected if the Nicheaddons Restaurant & Cafe Addon For Elementor plugin is installed with a version lower than 1.5.9 and Elementor is active on the site.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5.9 or later
Fixed in 1.5.9
Interim mitigation

Update the plugin to version 1.5.9 or later which contains the security fix. If unable to update immediately, disable the affected plugin or implement WAF rules to block XSS attack patterns.

Recommended fix High confidence

1.5.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Restaurant & Cafe Addon For Elementor' by nicheaddons
  4. Click 'Update now' when version 1.5.9 is available, or manually upload version 1.5.9 of the plugin
  5. Verify the update was successful and the plugin shows version 1.5.9

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Restaurant \& Cafe Addon For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54316 — 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-54316 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