
SaasLauncher · Security record
Is SaasLauncher safe?
No known vulnerability affects the current version (2.0.21). 1 issue was found in earlier versions and fixed, the latest disclosed on Sep 3, 2025.
Checked 2 days ago against the WPVulnerability database, for version 2.0.21.
How it’s looked after
- Last release
- Sep 28, 2026 (1 month ago)
- Releases in the last year
- 24
- Active installs
- 4K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in SaasLauncher
Newest first, with any that affect the current version at the top.
- medium
Missing Authorization
Fixed in 1.3.1 · CVE-2025-58606 · Sep 3, 2025 · Wordfence
Questions about SaasLauncher’s security
Is SaasLauncher safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep SaasLauncher updated: most attacks target sites that haven’t updated.
Does SaasLauncher have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep SaasLauncher up to date.
Is SaasLauncher still maintained?
Yes. Its last release was 1 month ago.
Hear about the next one first
Track your theme 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 theme updated.