Meta Extension Security & Risk Analysis

wordpress.org/plugins/meta-extensions

Allows adding custom form fields to posts, storing them in custom meta fields. Integrates NGG, WT, and WP-DM.

10 active installs v1.0.3 PHP + WP 2.0.2+ Updated Jul 11, 2010
custom-fieldsfieldsmetameta-fieldsposts
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Meta Extension Safe to Use in 2026?

Generally Safe

Score 85/100

Meta Extension has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 15yr ago
Risk Assessment

The "meta-extensions" v1.0.3 plugin demonstrates a generally strong security posture based on the provided static analysis. The plugin has no identified CVEs in its history, suggesting a commitment to security or a lack of past vulnerabilities. The attack surface is completely zero, with no AJAX handlers, REST API routes, shortcodes, or cron events, which significantly reduces the potential for external exploitation. Furthermore, the absence of dangerous functions, file operations, and external HTTP requests are all positive indicators.

However, there are notable concerns regarding its handling of SQL queries. All six SQL queries are executed without prepared statements, a significant risk that could lead to SQL injection vulnerabilities if any user-supplied data is incorporated into these queries. While the taint analysis shows no unsanitized paths, this might be due to the limited flows analyzed or the absence of user input reaching those specific SQL queries. The output escaping is also only 43% properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if dynamic content is not adequately sanitized before display.

In conclusion, while the plugin's minimal attack surface and clean vulnerability history are strengths, the reliance on raw SQL queries and insufficient output escaping present critical areas of concern that require immediate attention to prevent potential security breaches.

Key Concerns

  • SQL queries not using prepared statements
  • Low percentage of properly escaped output
Vulnerabilities
None known

Meta Extension Security Vulnerabilities

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

Meta Extension Code Analysis

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

SQL Query Safety

0% prepared6 total queries

Output Escaping

43% escaped7 total outputs
Data Flows
All sanitized

Data Flow Analysis

1 flows
<metaext.class> (metaext.class.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Meta Extension Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_headmetaext.php:49
actionsimple_edit_formmetaext.php:51
actionedit_form_advancedmetaext.php:52
actionedit_postmetaext.php:53
actionsave_postmetaext.php:54
actionpublish_postmetaext.php:55
Maintenance & Trust

Meta Extension Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedJul 11, 2010
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Meta Extension Developer Profile

sroyalty

1 plugin · 10 total installs

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

How We Detect Meta Extension

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/meta-extensions/admin.css

HTML / DOM Fingerprints

CSS Classes
metaext-span
FAQ

Frequently Asked Questions about Meta Extension