SlingBlocks · Security record
Is SlingBlocks safe?
No known vulnerability affects the current version (1.8.1). 3 issues were found in earlier versions and fixed, the latest disclosed on Aug 20, 2025.
Checked 3 days ago against the WPVulnerability database, for version 1.8.1.
How it’s looked after
- Last release
- May 23, 2026 (5 months ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.0.0
- Active installs
- 6K+
3 known vulnerabilities
- 3 medium
None affects the current version.
Disclosed each year
- 20241
- 20252
Every known vulnerability in SlingBlocks
Newest first, with any that affect the current version at the top.
Fixed in 1.7.0 · CVE-2025-8607 · Aug 20, 2025 · Wordfence
Fixed in 1.6.0 · CVE-2024-13675 · Mar 7, 2025 · Wordfence
Fixed in 1.5.0 · CVE-2024-38684 · Jul 10, 2024 · Wordfence
Questions about SlingBlocks’s security
Is SlingBlocks safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep SlingBlocks updated: most attacks target sites that haven’t updated.
Does SlingBlocks have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep SlingBlocks up to date.
Is SlingBlocks still maintained?
Yes. Its last release was 5 months ago. No support threads were opened in the last two months.
Is SlingBlocks compatible with the latest WordPress?
It’s tested up to WordPress 7.0.0, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.