Skip to main content
EPSS 0.3%top 83%

CVE-2026-17023: CWE-284 Improper Access Control in Salon Booking System

0
Medium
Published: 08/10/2026 (08/10/2026, 06:00:18 UTC)
Source: CVE Database V5
Product: Salon Booking System

Description

The Salon Booking System WordPress plugin through 10.30.33 does not perform any capability check or validate an OAuth state value on its Google Calendar authorization callback, which is also hooked for unauthenticated users, allowing an unauthenticated attacker to overwrite the site's stored Google Calendar connection tokens with attacker-controlled ones and hijack the integration. Exploitation requires the site to have configured its own Google OAuth client for the calendar feature.

CVSS v3.1

Score 4.8medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected software

Salon Booking System

Affected versions
>=0 <=10.30.33

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/17/2026, 15:09:14 UTC

Technical Analysis

The Salon Booking System WordPress plugin versions up to and including 10.30.33 contain an improper access control vulnerability (CWE-284) in the Google Calendar authorization callback. The callback does not verify user capabilities or validate the OAuth state parameter and is accessible to unauthenticated users. This allows attackers to replace the legitimate Google Calendar tokens stored by the site with malicious tokens under their control, effectively hijacking the integration. Successful exploitation depends on the site having configured its own Google OAuth client for the calendar feature.

Potential Impact

An unauthenticated attacker can overwrite the Google Calendar connection tokens stored by the vulnerable plugin, leading to hijacking of the calendar integration. This can result in limited integrity and availability impact on the calendar functionality. There is no direct confidentiality impact reported. The attack requires the site to have configured its own Google OAuth client, which limits the scope of affected installations.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the Google Calendar authorization callback endpoint if possible and monitor for suspicious activity related to OAuth token changes. Avoid configuring a custom Google OAuth client for the calendar feature if not necessary.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-07-24T10:19:45.313Z
State
PUBLISHED

Threat ID: 6a7972b0bf8831d5392fb03c

Added to database: 08/10/2026, 06:41:52 UTC

Last enriched: 08/17/2026, 15:09:14 UTC

Last updated: 09/25/2026, 01:47:41 UTC

Views: 26

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses