WP SEF Urls Security & Risk Analysis

wordpress.org/plugins/wp-sef-urls

Search Engine Friendly urls for Wordpress

30 active installs v0.1 PHP + WP 3.0.1+ Updated Oct 5, 2012
rewrite-urlssef
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP SEF Urls Safe to Use in 2026?

Generally Safe

Score 85/100

WP SEF 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 "wp-sef-urls" plugin v0.1 exhibits a seemingly strong security posture based on the provided static analysis. It boasts zero identified entry points from common attack vectors like AJAX handlers, REST API routes, shortcodes, and cron events. Furthermore, the absence of dangerous functions, file operations, external HTTP requests, and any recorded vulnerabilities in its history are positive indicators. The plugin also appears to be diligent in its use of prepared statements for SQL queries.

However, a significant concern arises from the complete lack of output escaping. This means that any data displayed to users, even if it doesn't originate from a direct user input, could potentially be injected with malicious content. The absence of nonce and capability checks across all potential (though currently zero) entry points also represents a potential weakness. While there are no reported vulnerabilities, this can sometimes indicate a lack of thorough security testing rather than inherent security. Therefore, while the plugin demonstrates good practices in some areas, the unescaped output is a critical oversight that introduces a tangible risk of cross-site scripting (XSS) vulnerabilities.

In conclusion, "wp-sef-urls" v0.1 has a very limited attack surface and appears to handle database interactions securely. The lack of vulnerability history is a positive sign. Nevertheless, the critical omission of output escaping represents a significant security flaw that requires immediate attention. The absence of explicit authorization checks on any potential future entry points also suggests a potential for insecure development practices if the plugin's functionality expands.

Key Concerns

  • 100% of outputs are not properly escaped
  • No capability checks found
  • No nonce checks found
Vulnerabilities
None known

WP SEF Urls Security Vulnerabilities

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

WP SEF Urls Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

WP SEF Urls Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

WP SEF Urls Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuwp-sef-urls.php:28
actioninitwp-sef-urls.php:74
filteruser_trailingslashitwp-sef-urls.php:85
filteruser_trailingslashitwp-sef-urls.php:93
Maintenance & Trust

WP SEF Urls Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedOct 5, 2012
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

WP SEF Urls Developer Profile

santiaga

3 plugins · 50 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 SEF 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 WP SEF Urls