WP Force SSL & HTTPS SSL Redirect · Security record
Is WP Force SSL & HTTPS SSL Redirect safe?
No known vulnerability affects the current version (1.70). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 7, 2024.
Checked 2 days ago against the WPVulnerability database, for version 1.70.
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
- 1 of 1 threads in two months
- Active installs
- 80K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in WP Force SSL & HTTPS SSL Redirect
Newest first, with any that affect the current version at the top.
Fixed in 1.67 · CVE-2024-5770 · Jun 7, 2024 · Wordfence
Questions about WP Force SSL & HTTPS SSL Redirect’s security
Is WP Force SSL & HTTPS SSL Redirect safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WP Force SSL & HTTPS SSL Redirect updated: most attacks target sites that haven’t updated.
Does WP Force SSL & HTTPS SSL Redirect have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep WP Force SSL & HTTPS SSL Redirect up to date.
Is WP Force SSL & HTTPS SSL Redirect still maintained?
Yes. Its last release was 2 months ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is WP Force SSL & HTTPS SSL Redirect 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.