Top Level Categories Security & Risk Analysis

wordpress.org/plugins/top-level-cats

This plugin allows you to remove the prefix before the URL to your category page (e.g. example.com/dogs instead of example.com/category/dogs)

2K active installs v1.0.1 PHP + WP 2.0.9+ Updated Nov 28, 2017
categoriespermalink
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Top Level Categories Safe to Use in 2026?

Generally Safe

Score 85/100

Top Level Categories has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The static analysis of the 'top-level-cats' plugin v1.0.1 reveals an exceptionally clean codebase with no identified attack surface points like AJAX handlers, REST API routes, shortcodes, or cron events. The code also demonstrates excellent security practices, with no dangerous functions, all SQL queries using prepared statements, and all outputs being properly escaped. Furthermore, there are no file operations, external HTTP requests, or recorded vulnerabilities (CVEs). This indicates a very strong security posture from a code implementation perspective.

However, the complete absence of nonce checks and capability checks across the entire plugin is a significant concern. While there are no direct entry points identified in this static analysis, the lack of these fundamental WordPress security mechanisms means that if any entry points were to be introduced in future updates or through developer error, they would be immediately susceptible to unauthorized access and manipulation. The vulnerability history being entirely clear is a positive indicator, suggesting a history of secure development. Despite the current lack of exploitability in the analyzed version, the absence of core security checks presents a potential weakness that should be addressed.

In conclusion, the 'top-level-cats' plugin v1.0.1 excels in its clean code and SQL hygiene, with no recorded vulnerabilities. Its strength lies in its minimal attack surface and well-written internal code. The primary weakness is the omission of essential WordPress security checks like nonces and capability checks. While not currently exploitable due to the lack of identified entry points, this absence leaves the plugin vulnerable should new entry points be added without corresponding security measures.

Key Concerns

  • Missing nonce checks on all potential entry points
  • Missing capability checks on all potential entry points
Vulnerabilities
None known

Top Level Categories Security Vulnerabilities

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

Top Level Categories 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

Top Level Categories Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
filtercategory_rewrite_rulestop-level-cats.php:18
filtergenerate_rewrite_rulestop-level-cats.php:19
filtercategory_linktop-level-cats.php:20
Maintenance & Trust

Top Level Categories Maintenance & Trust

Maintenance Signals

WordPress version tested2.5
Last updatedNov 28, 2017
PHP min version
Downloads91K

Community Trust

Rating100/100
Number of ratings4
Active installs2K
Developer Profile

Top Level Categories Developer Profile

Rock Lobster Inc.

60196 plugins · 349.8M total installs

73
trust score
Avg Security Score
92/100
Avg Patch Time
412 days
View full developer profile
Detection Fingerprints

How We Detect Top Level Categories

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

Asset Fingerprints

Version Parameters
top-level-cats/style.css?ver=top-level-cats/script.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Top Level Categories