Salon Booking SystemWordPress extension · Salonbookingsystem

CVE-2024-43280

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-19
Fix available
A fix is available. Upgrade to 10.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Salon Booking System Salon booking system.This issue affects Salon booking system: from n/a through 10.8.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 · moderate confidence

An open redirect vulnerability in the Salon Booking System allows attackers to craft malicious URLs that appear to originate from the legitimate booking site but redirect users to attacker-controlled domains. This can facilitate phishing attacks where users believe they are on the legitimate booking platform.

MitigationUpdate to the latest version of Salon Booking System once the patch is released, or implement strict URL validation to ensure all redirect targets are trusted, whitelisted domains.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate installed plugin version
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'Salon Booking System' in the list, and note the version number displayed
    Affected if The version shown is lower than 10.9 (e.g., 10.8, 10.7, earlier versions)
  2. Verify plugin is active
    In the same plugins list, confirm that Salon Booking System shows as 'Active' under the status column
    Affected if The plugin is active and the version is below 10.9
  3. Identify redirect-capable endpoints
    Review your web server access logs for requests containing parameters that may control redirects, such as 'redirect', 'url', 'target', or 'return' pointing to external domains
    Affected if Log analysis reveals unvalidated redirect parameters being used with external URLs while running a vulnerable version

Your environment is affected if the Salon Booking System plugin is installed and active at a version lower than 10.9, allowing external redirect targets to be crafted without validation.

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

Update to the latest version of Salon Booking System once the patch is released, or implement strict URL validation to ensure all redirect targets are trusted, whitelisted domains.

Recommended fix Moderate confidence

Version 10.9 or latest stable release

  1. 1. Create a complete backup of the Salon Booking System database and files
  2. 2. Download Salon Booking System version 10.9 or the latest stable release from the official source
  3. 3. Before upgrading, test the update in a staging/development environment to ensure compatibility
  4. 4. Install the update following the plugin's standard upgrade procedure
  5. 5. Clear any caching mechanisms if the site uses them
  6. 6. Verify that the open redirect vulnerability is resolved by testing the affected URL parameters
  7. 7. Monitor the site's functionality post-upgrade to ensure all booking features work correctly

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

Fix this in Salon Booking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43280 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