Salon Booking SystemWordPress extension · Salonbookingsystem
CVE-2024-37231
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Salon Booking System Salon booking system allows File Manipulation.This issue affects Salon booking system: from n/a through 9.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 confidenceA path traversal vulnerability in the Salon Booking System allows attackers to manipulate file path inputs to access or write files outside the intended directory. This could enable unauthorized reading of sensitive files or writing malicious files to the system, potentially leading to remote code execution.
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.0CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 panel, navigate to Plugins > Installed Plugins, and locate the Salon Booking System entry to view its version number. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comments.Affected if The displayed version number is less than 10.0 (for example, 9.x, 8.x, or any version below 10.0)
-
Verify if file upload functionality is accessibleCheck the Salon Booking System settings pages for file upload, import, backup, or export features. Look for options related to staff photo uploads, booking data import/export, or system backup functionality.Affected if File upload or file path manipulation features are enabled and accessible to users, especially unauthenticated or low-privileged users
-
Inspect file operation code for path traversal vulnerabilitiesIf you have access to the plugin source code, examine PHP functions that handle file paths (fopen, file_get_contents, include, require, move_uploaded_file) to see if they use user-supplied input without proper path sanitization (checking for ../ sequences or realpath() validation).Affected if The code accepts file path parameters without validating that resolved paths remain within an allowed directory
-
Test for path traversal in file-related featuresIf you have a testing environment, submit requests to file-related endpoints (such as file download, image loading, or data import) with path traversal sequences (for example, ../../wp-config.php) in path parameters to observe if unauthorized file access occurs.Affected if Requests with ../ sequences successfully return files outside the intended upload or content directory
-
Check server logs for suspicious file access patternsReview web server access logs (Apache, Nginx) and application logs for unusual patterns involving Salon Booking System endpoints with encoded or literal path traversal sequences in the request URI or parameters.Affected if Logs show requests to Salon Booking System files containing ../ patterns that successfully accessed files outside the plugin directory
You are affected if the Salon Booking System version is below 10.0 AND file upload or path-manipulation features are enabled and accessible without proper path validation.
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.0
Implement strict input validation using allowlisting and canonicalization to resolve path traversal sequences (../), ensuring all file operations are restricted to explicitly permitted directories.
10.0
- 1. Back up your WordPress database and files before performing any upgrade.
- 2. Download Salon Booking System version 10.0 or later from the official WordPress plugin repository or your purchase source.
- 3. Deactivate the existing Salon Booking System plugin through WordPress Admin > Plugins.
- 4. Delete the existing Salon Booking System plugin files (or overwrite via WordPress plugin upload interface).
- 5. Upload and install version 10.0 of the Salon Booking System plugin.
- 6. Activate the plugin and verify all booking functionalities work correctly.
- 7. Test that the path traversal vulnerability is remediated by confirming file access is properly restricted.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Salon Booking System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37231 — 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-37231 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