Crisp · Security record
Is Crisp safe?
No known vulnerability affects the current version (0.49). 2 issues were found in earlier versions and fixed, the latest disclosed on Mar 13, 2024.
Checked 2 days ago against the WPVulnerability database, for version 0.49.
How it’s looked after
- Last release
- Oct 21, 2026 (2 weeks ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 7.1.4
- Active installs
- 10K+
2 known vulnerabilities
- 1 high
- 1 medium
None affects the current version.
Disclosed each year
- 20211
- 20241
Every known vulnerability in Crisp
Newest first, with any that affect the current version at the top.
Fixed in 0.45 · CVE-2024-27963 · Mar 13, 2024 · Wordfence
Fixed in 0.32 · CVE-2021-43353 · Dec 16, 2021 · Wordfence
Questions about Crisp’s security
Is Crisp safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Crisp updated: most attacks target sites that haven’t updated.
Does Crisp have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Crisp up to date.
Is Crisp still maintained?
Yes. Its last release was 2 weeks ago. No support threads were opened in the last two months.
Is Crisp compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin 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 plugin updated.