dbcve.org
Salon Booking SystemWordPress extension · Salonbookingsystem

CVE-2024-30510

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 9.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Unrestricted Upload of File with Dangerous Type vulnerability in Salon Booking System Salon booking system.This issue affects Salon booking system: from n/a through 9.5.

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 confidence

Unrestricted file upload vulnerability in Salon Booking System allows attackers to upload dangerous file types (e.g., executable PHP scripts) without proper validation. This could enable remote code execution on the server.

MitigationImplement strict file type validation (whitelist approach), verify file MIME types and extensions, store uploads outside webroot or disable script execution in upload directories, and add content-type checking.

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
Salon Booking SystemWordPress extension
Affected:< 9.5.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Salon Booking System is installed
    Check your WordPress plugins directory or look for the 'salon-booking-system' folder in wp-content/plugins. You can also query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name = 'salon_version' OR option_name = 'active_plugins';
    Affected if The plugin is present and active on the WordPress site
  2. Identify the installed version
    Check the plugin header in salon-booking-system/salon-booking.php for the 'Version:' field, or query: SELECT option_value FROM wp_options WHERE option_name = 'salon_version'; Compare the version number to 9.5.1.
    Affected if The installed version is lower than 9.5.1 (e.g., 9.5.0, 9.4.x, etc.)
  3. Verify the file upload feature is accessible
    Check if the booking plugin's upload functionality is enabled. Look for settings related to 'attachments', 'file upload', or 'service images' in Salon > Settings. The vulnerability exists in the upload handler at /salon-booking-system includes/classes/../../../ajax.php or similar upload endpoints.
    Affected if Upload functionality is enabled and the plugin handles file attachments for bookings or services
  4. Inspect upload directory configuration
    Check the wp-content/uploads/salon directory (or custom upload path) to see if uploaded files are stored. Verify if .htaccess or web.config exists to prevent script execution in upload directories. If PHP files can be executed from this location, exploitation is possible.
    Affected if Upload directories allow script execution (no .htaccess blocking PHP execution, or files stored inside webroot without restrictions)
  5. Review server-side file type validation
    Examine the plugin's file upload handling code in includes/classes/SLNL_Attachment.class.php or similar. Look for MIME type validation, extension whitelist, and content-type header checking. Missing or weak validation indicates vulnerability.
    Affected if No whitelist-based file type validation exists, or only client-side checks are performed

You are affected if Salon Booking System plugin is installed with a version below 9.5.1 AND the file upload feature is enabled, allowing potentially malicious files to be uploaded and executed.

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 9.5.1 or later
Fixed in 9.5.1
Interim mitigation

Implement strict file type validation (whitelist approach), verify file MIME types and extensions, store uploads outside webroot or disable script execution in upload directories, and add content-type checking.

Recommended fix High confidence

9.5.1

  1. 1. Backup your WordPress database and files before performing any upgrade.
  2. 2. Download Salon Booking System version 9.5.1 or later from the official WordPress plugin repository or the vendor.
  3. 3. Update the plugin through WordPress admin dashboard (Plugins > Add New > Upload, or replace files via FTP).
  4. 4. Verify the update was successful by checking the plugins page shows version 9.5.1 or later.
  5. 5. Test file upload functionality to confirm the vulnerability is remediated.

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

Fix this in Salon Booking System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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