Force Lowercase URLs Security & Risk Analysis

wordpress.org/plugins/force-lowercase-urls

Perform a 301 redirect from an uppercase URL to the lowercase version for all non-admin, non-file URLs

200 active installs v1.0 PHP + WP 3.4+ Updated Nov 9, 2012
301redirects
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Force Lowercase URLs Safe to Use in 2026?

Generally Safe

Score 85/100

Force Lowercase URLs has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 13yr ago
Risk Assessment

The 'force-lowercase-urls' plugin v1.0 exhibits an excellent security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the attack surface. Furthermore, the code demonstrates strong security practices with zero dangerous functions, 100% of SQL queries using prepared statements, and all outputs being properly escaped. There are no file operations or external HTTP requests, and crucially, no use of nonces or capability checks were detected, which is generally a concern, but given the minimal attack surface, it doesn't present an immediate risk. The taint analysis found two flows with unsanitized paths but categorized them as critical and high severity zero, indicating no exploitable vulnerabilities were found in these flows.

The plugin's vulnerability history is also clean, with no recorded CVEs, past or present. This suggests a history of secure development or a lack of historical scrutiny, but no current known vulnerabilities is a positive sign. The plugin's strengths lie in its extremely limited attack surface and adherence to best practices in its code. However, the lack of any nonces or capability checks, while not currently exploitable due to the lack of entry points, could become a concern if the plugin's functionality were to expand in the future without the introduction of these essential security controls. Overall, this plugin appears to be very secure in its current state.

Key Concerns

  • Flows with unsanitized paths (no severity)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Force Lowercase URLs Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Force Lowercase URLs 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
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
storm_force_lowercase (force-lowercase-urls.php:16)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Force Lowercase URLs Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actioninitforce-lowercase-urls.php:13
Maintenance & Trust

Force Lowercase URLs Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedNov 9, 2012
PHP min version
Downloads3K

Community Trust

Rating90/100
Number of ratings4
Active installs200
Developer Profile

Force Lowercase URLs Developer Profile

Storm Consultancy

4 plugins · 810 total installs

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

How We Detect Force Lowercase URLs

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Force Lowercase URLs