NVD / CVE Program· CNA WPScan

CVE-2022-0919: Salon booking system < 7.6.3 - Unauthenticated Sensitive Data Disclosure

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The Salon booking system Free and pro WordPress plugins before 7.6.3 do not have proper authorisation when searching bookings, allowing any unauthenticated users to search other's booking, as well as retrieve sensitive information about the bookings, such as the full name, email and phone number of the person who booked it.

MediumCVSS 5.3 · v3.1—No exploit No fix recorded

Published: Apr 11, 2022
Updated: Jun 17, 2026
EPSS: 1.1% · 67th percentile
CWE: CWE-862

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

Is Salon Booking System – Appointment Booking for Salons, Barbershops & Spas on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
salonbookingsystem	salon booking system	cpe:2.3:a:salonbookingsystem:salon_booking_system

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

salonbookingsystem salon booking systembefore 7.6.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown Salon booking system
- 7.6.3 and later · before 7.6.3affected
Unknown Salon Booking System Pro
- 7.6.3 and later · before 7.6.3affected

Same product

salonbookingsystem: all records

Other highest-scoring records for the same primary product.

CVE-2024-3229Salon Booking System <= 10.2 - Unauthenticated Arbitrary File Upload
39Monitor
CVE-2024-30510WordPress Salon booking system plugin <= 9.5 - Arbitrary File Upload vulnerability
39Monitor
CVE-2024-37231WordPress Salon booking system plugin <= 9.9 - Arbitrary File Deletion vulnerability
36Monitor

Published before and after this one in the same product

← EarlierCVE-2021-24429Jul 12, 2021 · Salon Booking System < 6.3.1 - Unauthenticated Stored Cross-Site Scripting (XSS)
24Monitor
Later →CVE-2022-0920Apr 11, 2022 · Salon booking system < 7.6.3 - Customer+ Bookings/Customers Data Disclosure
30Monitor
Later →CVE-2022-43487Dec 5, 2022 · Cross-site scripting vulnerability in Salon booking system versions prior to 7.9 allows a remote unauthenticated attacker to inject an arbit
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

HuliCymetrics

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).