Amplified Meta Tags Security & Risk Analysis

wordpress.org/plugins/cf-meta-tags

A plugin created to help our publishers integrate our ad units using music data.

50 active installs v2.1.0 PHP + WP 3.7+ Updated Aug 18, 2020
amplifiedbandsintown-amplifiedbitbit-amplifiedtonefuse
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Amplified Meta Tags Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'cf-meta-tags' plugin v2.1.0 exhibits a strong security posture. The plugin demonstrates excellent adherence to best practices, with no identified attack surface points that lack authentication checks, no direct SQL queries without prepared statements, and a complete absence of dangerous functions, file operations, or external HTTP requests. The presence of a nonce check and a capability check further bolster its security. Taint analysis yielding zero flows with unsanitized paths, especially with no critical or high severity issues, indicates a low risk of remote code execution or data compromise originating from user-supplied input within the analyzed code paths.

The plugin's vulnerability history is equally reassuring, with zero recorded CVEs. This lack of past security incidents, coupled with no currently unpatched vulnerabilities, suggests a well-maintained and robust codebase. The absence of common vulnerability types further reinforces this positive assessment.

In conclusion, the 'cf-meta-tags' plugin v2.1.0 appears to be a secure option. Its minimal attack surface, diligent use of security features like nonce and capability checks, absence of exploitable taint flows, and clean vulnerability history collectively point to a low-risk plugin. The only minor concern is the 18% of outputs that are not properly escaped, which could potentially lead to cross-site scripting (XSS) vulnerabilities if the unescaped data originates from a untrusted source, though the lack of known vulnerabilities suggests this risk is currently mitigated or not being exploited.

Key Concerns

  • Improperly escaped output (18%)
Vulnerabilities
None known

Amplified Meta Tags Security Vulnerabilities

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

Amplified Meta Tags Code Analysis

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

Output Escaping

82% escaped11 total outputs
Attack Surface

Amplified Meta Tags Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadd_meta_boxescf_meta.php:285
actionsave_postcf_meta.php:287
actionwp_headcf_meta.php:289
Maintenance & Trust

Amplified Meta Tags Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedAug 18, 2020
PHP min version
Downloads13K

Community Trust

Rating0/100
Number of ratings0
Active installs50
Developer Profile

Amplified Meta Tags Developer Profile

muchenbit

1 plugin · 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 Amplified Meta Tags

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/cf-meta-tags/css/style.css/wp-content/plugins/cf-meta-tags/js/scripts.js
Script Paths
/wp-content/plugins/cf-meta-tags/js/scripts.js
Version Parameters
cf-meta-tags/css/style.css?ver=cf-meta-tags/js/scripts.js?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- Clickfuse Meta Tags -->
Data Attributes
name="cf_meta_artist"name="cf_meta_song"name="cf_meta_genre"name="cf_meta_tv_term"name="cf_meta_album"name="cf_meta_album_is"+2 more
FAQ

Frequently Asked Questions about Amplified Meta Tags