CVE-2024-4442
Salonbookingsystem Salon Booking System remote code execution
- Published21 May 2024
Description
The Salon booking system plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 9.8. This is due to the plugin not properly validating the path of an uploaded file prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible. This was partially patched in 9.9, and sufficiently patched in 10.0. CVE-2024-37231 appears to be a duplicate of this issue.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HAffected products
Remediation
References
- https://plugins.trac.wordpress.org/browser/salon-booking-system/tags/9.8/src/SLN/Action/Ajax/RemoveUploadedFile.php#L5
- https://plugins.trac.wordpress.org/changeset/3088196/salon-booking-system#file14
- https://plugins.trac.wordpress.org/changeset/3098413/salon-booking-system/trunk/src/SLN/Action/Ajax/RemoveUploadedFile.php
- https://www.wordfence.com/threat-intel/vulnerabilities/id/eaafeadd-f44c-49b1-b900-ef40800c629e?source=cve
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-4442 being actively exploited?
CVE-2024-4442 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.24%.
How severe is CVE-2024-4442?
CVE-2024-4442 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 1.24% probability of exploitation.
Which products are affected by CVE-2024-4442?
Affected products include Salonbookingsystem Salon Booking System.
How do I fix CVE-2024-4442?
Upgrade affected software to a fixed version, for example Salonbookingsystem Salon Booking System 10.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-4442 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.