CVE-2026-3658
7.5Croixhaug · Simply Schedule Appointments Booking Plugin
The Simply Schedule Appointments Booking Plugin for WordPress is vulnerable to unauthenticated SQL injection via the fields parameter, allowing for unauthorized database information extraction.
Executive summary
A critical SQL injection vulnerability in the Simply Schedule Appointments Booking Plugin for WordPress allows unauthenticated attackers to exfiltrate sensitive database information.
Vulnerability
This vulnerability is an improper neutralization of special elements used in an SQL command (CWE-89) affecting the fields parameter. It allows unauthenticated attackers to manipulate existing SQL queries to extract sensitive data such as usernames, email addresses, and password hashes.
Business impact
The ability for an unauthenticated attacker to extract sensitive user information poses a significant risk to data confidentiality and regulatory compliance. With a CVSS score of 7.5, this high-severity flaw could lead to full account takeovers or the compromise of administrative credentials. Such a breach typically results in severe reputational damage and potential legal liabilities regarding data protection standards.
Remediation
Immediate Action: Administrators should immediately audit the installation and remove the plugin if it is not business critical. If the plugin is required, monitor for vendor updates that address the identified flaw in the class-td-db-model.php file.
Proactive Monitoring: Review database query logs for suspicious patterns or unexpected syntax involving the fields parameter. Alerting should be configured for unusual database access requests originating from external IP addresses.
Compensating Controls: Deploy a Web Application Firewall (WAF) with updated rulesets designed to detect and block SQL injection attempts targeting WordPress plugins. This can provide a necessary layer of protection while awaiting a permanent software patch.
Exploitation status
Public Exploit Available: No (exploit_available unknown).
Analyst recommendation
Given the high CVSS score and the sensitive nature of the data exposed, organizations must prioritize the mitigation of this vulnerability. If an official patch is not yet available, the safest course of action is to disable or remove the plugin from the environment to prevent unauthorized data access. Security teams should remain vigilant for vendor-provided updates and apply them as soon as they are released to restore the security posture of the WordPress instance.
Sources
Originally found and disclosed by momopon1415, per the CVE Program record.