Splide Carousel Block · Security record
Is Splide Carousel Block safe?
No known vulnerability affects the current version (1.8.0). 1 issue was found in earlier versions and fixed, the latest disclosed on May 26, 2026.
Checked 2 days ago against the WPVulnerability database, for version 1.8.0.
How it’s looked after
- Last release
- Aug 27, 2026 (2 months ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 4K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Splide Carousel Block
Newest first, with any that affect the current version at the top.
Fixed in 1.7.2 · CVE-2026-9022 · May 26, 2026 · Wordfence
Questions about Splide Carousel Block’s security
Is Splide Carousel Block safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Splide Carousel Block updated: most attacks target sites that haven’t updated.
Does Splide Carousel Block have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Splide Carousel Block up to date.
Is Splide Carousel Block still maintained?
Yes. Its last release was 2 months ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Splide Carousel Block 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.