
Appointment · Security record
Is Appointment safe?
One known vulnerability affects the current version (3.7.6), and it has no fix yet.
Checked 5 days ago against the WPVulnerability database, for version 3.7.6.
How it’s looked after
- Last release
- Aug 30, 2026 (2 months ago)
- Releases in the last year
- 5
- Active installs
- 2K+
3 known vulnerabilities
- 1 critical
- 2 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20221
- 20261
Every known vulnerability in Appointment
Newest first, with any that affect the current version at the top.
- critical
Cross-Site Request Forgery
Affects the current version · No fix yet · CVE-2026-39620 · Feb 11, 2026 · Wordfence
Fixed in 3.2.6 · Feb 14, 2022 · Wordfence
Fixed in 3.2.6 · WPScan
Questions about Appointment’s security
Is Appointment safe to use?
Yes: 1 known vulnerability affects version 3.7.6, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Appointment have known security vulnerabilities?
Yes: 1 known vulnerability affects version 3.7.6, according to WPVulnerability’s database.
Is Appointment still maintained?
Yes. Its last release was 2 months ago.
Hear about the next one first
Track your theme on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every theme updated.