JSM Force HTTP to HTTPS / SSL · Security record
Is JSM Force HTTP to HTTPS / SSL safe?
No known vulnerabilities are on record for JSM Force HTTP to HTTPS / SSL.
Checked 2 days ago against the WPVulnerability database, for version 3.5.0.
How it’s looked after
- Last release
- Oct 29, 2026 (1 week ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.1.4
- Active installs
- 6K+
Known vulnerabilities
None on record for JSM Force HTTP to HTTPS / SSL.
Questions about JSM Force HTTP to HTTPS / SSL’s security
Is JSM Force HTTP to HTTPS / SSL safe to use?
No known vulnerabilities are on record for JSM Force HTTP to HTTPS / SSL. That isn’t a guarantee, so keep it updated like any plugin.
Does JSM Force HTTP to HTTPS / SSL have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for JSM Force HTTP to HTTPS / SSL.
Is JSM Force HTTP to HTTPS / SSL still maintained?
Yes. Its last release was 1 week ago. No support threads were opened in the last two months.
Is JSM Force HTTP to HTTPS / SSL 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.