WP REST API Force SSL Security & Risk Analysis

wordpress.org/plugins/json-rest-api-force-ssl

Force WP REST API endpoints to only be served over HTTPS.

10 active installs v0.2.0 PHP + WP 4.4+ Updated Apr 20, 2016
apijsonrestrest-apiwp-api
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP REST API Force SSL Safe to Use in 2026?

Generally Safe

Score 85/100

WP REST API Force SSL has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The static analysis of the "json-rest-api-force-ssl" plugin v0.2.0 reveals a very clean codebase with no identified vulnerabilities or risky patterns. The plugin demonstrates excellent security practices, including the complete absence of dangerous functions, file operations, and external HTTP requests. Furthermore, all SQL queries are properly prepared, and all output is correctly escaped, mitigating common web application vulnerabilities. The attack surface is also minimal, with no AJAX handlers, REST API routes, shortcodes, or cron events exposed, and importantly, none of these entry points are unprotected.

Taint analysis shows zero identified flows, indicating that user input is not being improperly handled or used in a way that could lead to exploits. The plugin's vulnerability history is also clear, with no recorded CVEs. This lack of historical issues, combined with the positive static analysis, suggests a well-developed and secure plugin. However, the absence of nonce and capability checks on the limited entry points, while not a direct issue given their zero count, is a pattern to note for future development, as it could become a risk if entry points are added without proper security measures. Overall, this plugin presents a low-risk profile.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

WP REST API Force SSL Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

WP REST API Force SSL Release Timeline

v0.2.0Current
v0.1.1
v0.1.0
Code Analysis
Analyzed Mar 16, 2026

WP REST API Force SSL Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0
Attack Surface

WP REST API Force SSL Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionrest_api_initjson-rest-api-force-ssl.php:34
Maintenance & Trust

WP REST API Force SSL Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedApr 20, 2016
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

WP REST API Force SSL Developer Profile

Frankie Jarrett

5 plugins · 2K total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect WP REST API Force SSL

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/json-rest-api-force-ssl/json-rest-api-force-ssl.php

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about WP REST API Force SSL