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