WCS Custom Permalinks Hotfix Security & Risk Analysis

wordpress.org/plugins/wcs-custom-permalinks-hotfix

After upgrading to WordPress 3.1.x, many installations suffer broken permalinks for categories and tags. This hotfix repairs the problem.

60 active installs v1.1 PHP + WP 3.0.0+ Updated May 8, 2011
canonical-redirectcategoriespermalinkspermalinks-bugpermalinks-not-working
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WCS Custom Permalinks Hotfix Safe to Use in 2026?

Generally Safe

Score 85/100

WCS Custom Permalinks Hotfix has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The plugin "wcs-custom-permalinks-hotfix" v1.1 exhibits a strong security posture based on the provided static analysis. The absence of any detected dangerous functions, raw SQL queries, or unsanitized taint flows suggests a well-developed and secure codebase. Furthermore, all identified output is properly escaped, and the plugin does not perform file operations or external HTTP requests, minimizing potential attack vectors. The presence of a capability check, even if only one is noted, is a positive sign for access control.

The vulnerability history also indicates a clean record, with no known CVEs ever recorded for this plugin. This lack of past vulnerabilities, coupled with the current static analysis findings, paints a picture of a plugin that has been developed with security in mind and has maintained this standard over time. The total absence of an attack surface, including AJAX handlers, REST API routes, and shortcodes, is a significant strength. However, the lack of any nonces detected might be a slight concern if there were any interaction points that would typically require them, although the absence of an attack surface might explain this.

In conclusion, "wcs-custom-permalinks-hotfix" v1.1 appears to be a very secure plugin. Its strengths lie in its minimal attack surface, robust code sanitization, and lack of historical vulnerabilities. The only minor point to potentially consider is the complete absence of nonce checks, which, in the context of zero attack surface, is not a direct risk but could be an oversight if future functionality is added. Overall, the risk associated with this plugin is very low.

Vulnerabilities
None known

WCS Custom Permalinks Hotfix Security Vulnerabilities

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

WCS Custom Permalinks Hotfix Code Analysis

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

Output Escaping

100% escaped1 total outputs
Attack Surface

WCS Custom Permalinks Hotfix Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actioninitwcs-custom-permalinks-hotfix.php:76
actionadmin_menuwcs-custom-permalinks-hotfix.php:224
Maintenance & Trust

WCS Custom Permalinks Hotfix Maintenance & Trust

Maintenance Signals

WordPress version tested3.1.4
Last updatedMay 8, 2011
PHP min version
Downloads10K

Community Trust

Rating100/100
Number of ratings1
Active installs60
Developer Profile

WCS Custom Permalinks Hotfix Developer Profile

Luke America

1 plugin · 60 total installs

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

How We Detect WCS Custom Permalinks Hotfix

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

Asset Fingerprints

HTML / DOM Fingerprints

HTML Comments
<!-- WCS Custom Permalinks Hotfix --><!-- Copyright (c) 2011 WP Code Snippets / Gizmo Digital Fusion (LukeAmerica2020@gmail.com) --><!-- This program is free software; you can redistribute it and/or modify it --><!-- under the terms of the GNU General Public License as published by the -->+32 more
FAQ

Frequently Asked Questions about WCS Custom Permalinks Hotfix