Media Meta & Force Regenerate Security & Risk Analysis

wordpress.org/plugins/media-meta

Displays the metadata information in the Media Library. Regenerates the metadata and thumbnails even if they exist.

200 active installs v0.0.3 PHP 7.0+ WP 4.8+ Updated Feb 9, 2020
forcemediametametadataregenerate
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Media Meta & Force Regenerate Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The "media-meta" plugin v0.0.3 presents a mixed security profile. On the positive side, the static analysis reveals no directly exploitable entry points like AJAX handlers, REST API routes, or shortcodes without proper authentication or permission checks. The absence of dangerous functions, SQL queries executed without prepared statements, file operations, and external HTTP requests further contribute to a seemingly robust security posture in these areas. The presence of a nonce check is also a good sign.

However, a significant concern arises from the complete lack of output escaping across all identified outputs. This suggests a high risk of Cross-Site Scripting (XSS) vulnerabilities, where unsanitized data displayed to users could be manipulated to execute malicious scripts. While the taint analysis did not reveal any unsanitized paths in the limited flow analyzed, the pervasive output escaping deficiency is a critical weakness. The plugin's vulnerability history shows no recorded CVEs, which is encouraging, but this could also be due to its limited feature set or lack of widespread use and auditing.

In conclusion, while "media-meta" v0.0.3 has successfully mitigated many common WordPress plugin vulnerabilities, the critical oversight in output escaping creates a significant attack surface for XSS. The lack of recorded vulnerabilities should not be interpreted as guaranteed security, especially given this identified weakness. Future development should prioritize implementing proper output escaping for all user-facing data.

Key Concerns

  • Output escaping is not implemented
Vulnerabilities
None known

Media Meta & Force Regenerate Security Vulnerabilities

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

Media Meta & Force Regenerate Code Analysis

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

Output Escaping

0% escaped6 total outputs
Data Flows
All sanitized

Data Flow Analysis

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

Media Meta & Force Regenerate Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionplugins_loadedcore.php:9
actionwp_loadedcore.php:10
filtermanage_media_columnscore.php:14
actionmanage_media_custom_columncore.php:15
actionadmin_headcore.php:16
actionadmin_footercore.php:17
actionwp_loadedcore.php:18
Maintenance & Trust

Media Meta & Force Regenerate Maintenance & Trust

Maintenance Signals

WordPress version tested5.3.21
Last updatedFeb 9, 2020
PHP min version7.0
Downloads5K

Community Trust

Rating100/100
Number of ratings5
Active installs200
Developer Profile

Media Meta & Force Regenerate Developer Profile

Jordy Meow

27 plugins · 371K total installs

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

How We Detect Media Meta & Force Regenerate

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
media-metadata-buttonmedia-metadata-togglemedia-metadataclosed
Data Attributes
data-mmt_regenerate
FAQ

Frequently Asked Questions about Media Meta & Force Regenerate