CVE-2026-3658
SQL Injection in Simply Schedule Appointments Plugin Exposes Data
Publication date: 2026-03-19
Last updated on: 2026-03-19
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| simply_schedule_appointments | simply_schedule_appointments | to 1.6.10.0 (inc) |
| simply_schedule_appointments | simply_schedule_appointments | 1.6.10.2 |
| simply_schedule_appointments | simply_schedule_appointments | 1.6.9.6 |
| simply_schedule_appointments | simply_schedule_appointments | 2.9.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know
Can you explain this vulnerability to me?
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin for WordPress is vulnerable to SQL Injection via the 'fields' parameter in all versions up to and including 1.6.10.0.
This vulnerability exists because the plugin does not properly escape user-supplied input and does not sufficiently prepare the existing SQL query.
As a result, unauthenticated attackers can append additional SQL queries to existing ones, potentially extracting sensitive information such as usernames, email addresses, and password hashes from the database.
How can this vulnerability impact me? :
This SQL Injection vulnerability allows unauthenticated attackers to extract sensitive data from the plugin's database.
- Exposure of usernames
- Exposure of email addresses
- Exposure of password hashes
Such data exposure can lead to further attacks, including account compromise, phishing, and identity theft.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know