Salon Booking SystemWordPress extension · Salonbookingsystem
CVE-2024-47316
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in Dimitri Grassi Salon booking system salon-booking-system.This issue affects Salon booking system: from n/a through <= 10.9.
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 confidenceAuthorization bypass vulnerability in the Salon booking system where user-controlled keys allow attackers to manipulate authorization checks. This could enable unauthorized access to booking data, user information, or administrative functions by modifying parameter values that the application uses for access control decisions.
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
< 10.9.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Salon Booking System versionAccess the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'Salon Booking System' and note the version number displayed, or inspect the plugin's main PHP file (salon-booking-system.php) to read the 'Version' header comment.Affected if The version number is lower than 10.9.1 (e.g., 10.8, 10.7, etc.)
-
Locate the plugin files on the serverNavigate to wp-content/plugins/salon-booking-system in your WordPress installation directory. Confirm the presence of the plugin files and note the last modification date of the main plugin file.Affected if The plugin is present and the installed version (from Step 1) is below 10.9.1
-
Review booking functionality access patternsExamine the plugin's booking submission forms and API endpoints (typically in includes/ or src/ directories) to identify parameters or keys used in authorization checks. Look for any $_GET, $_POST, or $_REQUEST variables that control access to booking data.Affected if User-controlled parameters (such as booking IDs, user IDs, or access tokens passed via GET/POST) are used directly in authorization logic without validation
-
Verify external booking access configurationsCheck the plugin settings under the WordPress admin for any 'Allow external access' or 'API access' options. Inspect the plugin's ajax handlers and REST API routes (often in ajax.php or includes/class-ajax.php) to determine if unauthenticated or low-privilege users can submit or retrieve booking information.Affected if External API or ajax endpoints are enabled and accept user-supplied identifiers without proper ownership verification
Your environment is affected if the Salon Booking System plugin version is below 10.9.1 and the system uses user-supplied parameters in authorization logic without validating that the requesting user owns or is authorized to access the requested booking/resource.
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.
dbcve · scoped10.9.1
Update the Salon booking system to a version beyond 10.9 that contains the security patch, or implement proper validation and authorization checks on all user-controlled keys/parameters to ensure users can only access resources they are authorized for.
10.9.1
- Upgrade the Salon Booking System plugin to version 10.9.1 or later to remediate the IDOR vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Salon Booking System
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47316 — 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-47316 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