The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'append_where_sql' parameter in all versions up to, and including, 1.6.11.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The /appointments/bulk REST endpoint is reachable by unauthenticated attackers because its permission check accepts a public nonce that is embedded in the booking widget's frontend JavaScript (ssa.api.public_nonce) and visible to all site visitors; exploitation requires issuing the request as a PUT with an application/x-www-form-urlencoded body so that PHP's superglobals are not populated and the blocklist check silently passes.
CVE-2026-7797
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 42.5%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
May 28, 2026
References (11)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.10.2/includes/lib/td-util/class-td-api-model.php#L304
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.10.2/includes/lib/td-util/class-td-api-model.php#L361
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.10.2/includes/lib/td-util/class-td-db-model.php#L1049
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.11.2/includes/lib/td-util/class-td-api-model.php#L304
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.11.2/includes/lib/td-util/class-td-api-model.php#L361
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/tags/1.6.11.2/includes/lib/td-util/class-td-db-model.php#L1049
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-api-model.php#L304
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-api-model.php#L361
- security@wordfencehttps://plugins.trac.wordpress.org/browser/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-db-model.php#L1049
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3549843/simply-schedule-appointments/tags/1.6.11.9/includes/lib/td-util/class-td-db-model.php
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/db3bddbd-44b0-4105-9039-0d669d643481?source=cve
Vendor Advisories for CVE-2026-7797(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 72× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 160 total refreshes for this CVE.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:37 UTCEG score recompute
- 2026-07-11 21:37 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 18:42 UTCEG score recompute
- 2026-07-08 18:41 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-02 14:31 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-02 14:31 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 14:59 UTCEG score recompute
- 2026-07-01 14:58 UTCGHSA enrichment
- 2026-07-01 03:25 UTCEG score recompute
- 2026-07-01 03:25 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 02:14 UTCEG score recompute
- 2026-06-30 02:14 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:47 UTCEG score recompute
- 2026-06-29 13:47 UTCGHSA enrichment
- 2026-06-28 18:41 UTCEG score recompute
- 2026-06-28 18:41 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 06:01 UTCEG score recompute
- 2026-06-28 06:01 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:21 UTCEG score recompute
- 2026-06-27 18:21 UTCGHSA enrichment
- 2026-06-27 05:31 UTCEG score recompute
- 2026-06-27 05:31 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:55 UTCEG score recompute
- 2026-06-26 16:55 UTCGHSA enrichment
- 2026-06-25 22:48 UTCEG score recompute
- 2026-06-25 22:48 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-25 11:04 UTCEG score recompute
- 2026-06-25 11:03 UTCGHSA enrichment
- 2026-06-24 22:56 UTCEG score recompute
- 2026-06-24 22:56 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 02:21 UTCEG score recompute
- 2026-06-18 02:21 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 14:50 UTCEG score recompute
- 2026-06-17 14:50 UTCGHSA enrichment
- 2026-06-17 03:18 UTCEG score recompute
- 2026-06-17 03:18 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 15:47 UTCEG score recompute
- 2026-06-16 15:47 UTCGHSA enrichment
- 2026-06-16 00:39 UTCEG score recompute
- 2026-06-16 00:39 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 13:08 UTCEG score recompute
- 2026-06-15 13:07 UTCGHSA enrichment
- 2026-06-15 01:13 UTCEG score recompute
- 2026-06-15 01:13 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 13:42 UTCEG score recompute
- 2026-06-14 13:42 UTCGHSA enrichment
- 2026-06-14 02:10 UTCEG score recompute
- 2026-06-14 02:09 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 14:37 UTCEG score recompute
- 2026-06-13 14:37 UTCGHSA enrichment
- 2026-06-13 03:04 UTCEG score recompute
- 2026-06-13 03:04 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 15:32 UTCEG score recompute
- 2026-06-12 15:32 UTCGHSA enrichment
- 2026-06-12 04:01 UTCEG score recompute
- 2026-06-12 04:01 UTCGHSA enrichment
- 2026-06-11 16:30 UTCEG score recompute
- 2026-06-11 16:30 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-7797?
When was CVE-2026-7797 disclosed?
Is CVE-2026-7797 actively exploited?
What is the CVSS score of CVE-2026-7797?
How do I remediate CVE-2026-7797?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-7797
Is Your Infrastructure Affected by CVE-2026-7797?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.