Stored XSS in Smart Appointment & Booking WordPress plugin (saab_save_form_data AJAX)
The Smart Appointment & Booking plugin for WordPress is vulnerable to stored cross-site scripting (XSS) via the saab_save_form_data AJAX action in all versions up to and including 1.0.7. The issue is caused by insufficient input sanitization and output escaping of user-supplied attributes, allowing an authenticated attacker (Subscriber role or higher) to inject arbitrary script content that is stored and later executed in victims’ browsers when they access an affected page.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
saab_save_form_data AJAX endpoint. Enforce a strict Content Security Policy (CSP) to reduce the impact of any injected script that might execute.Remediation
Patch, then assume compromise.
saab_save_form_data AJAX action. If no fixed version is available, remove/disable the plugin.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.