FitConsent CMP Security & Risk Analysis

wordpress.org/plugins/fitconsent-cmp

Integrates FitConsent with WordPress and the WP Consent API for seamless Google Site Kit compatibility.

0 active installs v1.0.3 PHP + WP 5.8+ Updated Dec 16, 2025
cmpconsent-modefitconsentgdpruser-consent-management-platform
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is FitConsent CMP Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 3mo ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'fitconsent-cmp' v1.0.3 plugin exhibits a strong security posture in several key areas. The absence of known CVEs and a clean vulnerability history suggests a commitment to security or a lack of identified weaknesses to date. Furthermore, the code analysis reveals no identified dangerous functions, no SQL queries outside of prepared statements, and no file operations or external HTTP requests, all of which significantly reduce the potential for common attack vectors. The lack of identified taint flows also indicates that sensitive data is not being improperly handled within the analyzed code paths.

However, there are areas that warrant attention. The fact that 43% of output is not properly escaped presents a notable risk of Cross-Site Scripting (XSS) vulnerabilities. While the attack surface appears small and has no unprotected entry points according to this analysis, the lack of any capability checks or nonce checks on entry points (even if they are currently zero) is a concern. Should future development introduce new entry points or if the current zero count is an artifact of the analysis scope, the absence of these fundamental security controls would create significant vulnerabilities. The current score reflects strengths in avoiding common pitfalls but highlights a significant weakness in output sanitization and a potential future risk due to missing common security checks.

Key Concerns

  • Significant unescaped output detected
  • No capability checks detected
  • No nonce checks detected
Vulnerabilities
None known

FitConsent CMP Security Vulnerabilities

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

FitConsent CMP Code Analysis

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

Output Escaping

57% escaped14 total outputs
Attack Surface

FitConsent CMP Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionwp_headfitconsent-cmp.php:48
actionwp_enqueue_scriptsfitconsent-cmp.php:80
actionplugins_loadedfitconsent-cmp.php:114
actionadmin_menuincludes\admin-settings.php:22
actionadmin_initincludes\admin-settings.php:49
Maintenance & Trust

FitConsent CMP Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 16, 2025
PHP min version
Downloads314

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

FitConsent CMP Developer Profile

DIGITLOAD

1 plugin · 0 total installs

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

How We Detect FitConsent CMP

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/fitconsent-cmp/js/integration.js
Script Paths
https://app.fitconsent.com/api/banner
Version Parameters
fitconsent-cmp/js/integration.js?ver=

HTML / DOM Fingerprints

JS Globals
gtagdataLayer
FAQ

Frequently Asked Questions about FitConsent CMP