SVGator · Security record
Is SVGator safe?
No known vulnerability affects the current version (1.4.0). 2 issues were found in earlier versions and fixed, the latest disclosed on May 24, 2024.
Checked 1 day ago against the WPVulnerability database, for version 1.4.0.
How it’s looked after
- Last release
- Oct 19, 2026 (2 weeks ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Active installs
- 1K+
2 known vulnerabilities
- 2 medium
None affects the current version.
Disclosed each year
- 20231
- 20241
Every known vulnerability in SVGator
Newest first, with any that affect the current version at the top.
Fixed in 1.3.0 · CVE-2024-4271 · May 24, 2024 · Wordfence
Fixed in 1.2.5 · CVE-2023-48766 · Nov 28, 2023 · Wordfence
Questions about SVGator’s security
Is SVGator safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep SVGator updated: most attacks target sites that haven’t updated.
Does SVGator have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep SVGator up to date.
Is SVGator still maintained?
Yes. Its last release was 2 weeks ago. No support threads were opened in the last two months.
Is SVGator 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.