VNEcategory Security & Risk Analysis

wordpress.org/plugins/vnecategory

Show category and subcategory and post in these categories

10 active installs v1.0 PHP + WP 2.8+ Updated Dec 14, 2012
categoryeach-categoryeach-postpost-in-sub-categorysub-category
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is VNEcategory Safe to Use in 2026?

Generally Safe

Score 85/100

VNEcategory 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 "vnecategory" v1.0 plugin exhibits a mixed security posture. On the positive side, it has a minimal attack surface with no reported CVEs, external requests, file operations, or cron events, suggesting a potentially safe design. All SQL queries are prepared, and there are no recorded vulnerabilities, which is a strong indicator of good development practices or a lack of extensive prior security analysis.

However, significant concerns arise from the static analysis. The presence of `create_function` is a critical security flaw, as it can lead to arbitrary code execution if user-supplied input is passed to it without proper sanitization. Furthermore, the plugin has a very low rate of output escaping (only 8%), leaving it highly susceptible to Cross-Site Scripting (XSS) vulnerabilities. The complete absence of nonce and capability checks across all entry points (even though the attack surface appears to be zero) means that if any entry points were to be introduced or exposed in future updates or through other means, they would be completely unprotected.

In conclusion, while the plugin's current known vulnerability history is clean and it demonstrates good practices in SQL handling and a limited attack surface, the identified `create_function` usage and the severely inadequate output escaping present substantial risks. These issues, if exploited, could lead to arbitrary code execution and widespread XSS attacks, overriding the benefits of its otherwise clean record.

Key Concerns

  • Use of dangerous create_function
  • Very low output escaping rate (8%)
  • No nonce checks on entry points
  • No capability checks on entry points
Vulnerabilities
None known

VNEcategory Security Vulnerabilities

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

VNEcategory Release Timeline

No version history available.
Code Analysis
Analyzed Mar 17, 2026

VNEcategory Code Analysis

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

Dangerous Functions Found

create_functionadd_action( 'widgets_init', create_function('', 'return register_widget("VNEcategory");') );vn_category.php:215

Output Escaping

8% escaped26 total outputs
Attack Surface

VNEcategory Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwidgets_initvn_category.php:215
Maintenance & Trust

VNEcategory Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedDec 14, 2012
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

VNEcategory Developer Profile

drmen8x

2 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 VNEcategory

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/vnecategory/vne_category.css

HTML / DOM Fingerprints

CSS Classes
vne_boxvne_box_headervne_parentvne_subvne_headingvne_thumbvne_descvne_box_list
HTML Comments
<!-- vne_box_<?php echo $id; ?> --><!-- End vne_box_<?php echo $id; ?> -->
Data Attributes
id="vne_box_"id="vne_box_header_"name="cat"name="show_sub"name="vne_num"name="sort_by"+2 more
FAQ

Frequently Asked Questions about VNEcategory