MetaParsedown Security & Risk Analysis

wordpress.org/plugins/metaparsedown

Import markdown and markdown-extra documents to Wordpress posts and pages, output as HTML, parse and save YAML front matter to post_meta, tags, and (o …

0 active installs v1.0.0 PHP 7.0+ WP 5.0+ Updated Nov 5, 2019
markdownmarkdown-extrametaparsedownparsedownparsedown-extra
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MetaParsedown Safe to Use in 2026?

Generally Safe

Score 85/100

MetaParsedown 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 "metaparsedown" v1.0.0 plugin exhibits a generally strong security posture with no known vulnerabilities and a robust approach to SQL queries and output escaping. The static analysis reveals a very small attack surface, with all identified entry points being protected. The absence of external HTTP requests and file operations also contributes positively to its security. However, a significant concern arises from the presence of the "unserialize" function, which, if used with untrusted input, can lead to serious security vulnerabilities such as remote code execution. Furthermore, the complete lack of nonce checks and capability checks across all identified entry points is a critical oversight. While the plugin has no recorded vulnerability history, this does not negate the inherent risks associated with using dangerous functions without proper validation and authorization mechanisms. The plugin's strengths lie in its limited attack surface and secure handling of common data interactions, but these are overshadowed by the potential dangers of unserialize and the absence of essential security controls.

Key Concerns

  • Dangerous function 'unserialize' found
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

MetaParsedown Security Vulnerabilities

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

MetaParsedown Release Timeline

v1.0.0Current
Code Analysis
Analyzed Mar 17, 2026

MetaParsedown Code Analysis

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

Dangerous Functions Found

unserializereturn unserialize(self::parseScalar(substr($scalar, 12)));Metaparsedown\Symfony\Component\Yaml\Inline.php:582

Output Escaping

100% escaped3 total outputs
Attack Surface

MetaParsedown Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[metaparsedown] Metaparsedown\MetaparsedownPlugin.php:55
WordPress Hooks 1
actionadmin_noticesMetaparsedown\MetaparsedownException.php:18
Maintenance & Trust

MetaParsedown Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedNov 5, 2019
PHP min version7.0
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

MetaParsedown Developer Profile

pagerange

1 plugin · 0 total installs

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

How We Detect MetaParsedown

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
metaparsedown
Shortcode Output
<div class="metaparsedown"> %s
FAQ

Frequently Asked Questions about MetaParsedown