Finsbury Media Cookie Consent Security & Risk Analysis

wordpress.org/plugins/finsbury-media-cookie-consent

Lightweight cookie banner with Google, Bing, and Clarity consent support and optional customization.

0 active installs v1.2.2 PHP 8.0+ WP 6.3+ Updated Unknown
cookie-consentfinsbury-mediagoogle-consent-mode-v2microsoft-claritymicrosoft-uet
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Finsbury Media Cookie Consent Safe to Use in 2026?

Generally Safe

Score 100/100

Finsbury Media Cookie Consent has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The "finsbury-media-cookie-consent" v1.2.2 plugin exhibits a mixed security posture. On the positive side, it demonstrates good practices regarding SQL queries, exclusively using prepared statements, and shows a high percentage of properly escaped output. There are no recorded historical vulnerabilities or CVEs, suggesting a history of stable and secure code. However, significant concerns arise from the attack surface analysis. The plugin exposes two AJAX handlers, both of which lack authentication checks. This is a critical oversight, as it allows any user, authenticated or not, to potentially trigger these handlers, leading to unauthorized actions.

The taint analysis reveals two flows with unsanitized paths, though they are not categorized as critical or high severity. This, combined with the lack of nonce checks on the AJAX handlers, presents a potential pathway for cross-site request forgery (CSRF) or other injection-style attacks if the unsanitized paths are exploitable. The presence of file operations and an external HTTP request, while not inherently insecure, increases the potential for exploits if combined with the unprotected entry points.

Overall, while the plugin avoids common pitfalls like raw SQL and outdated libraries, the two unprotected AJAX handlers are a significant vulnerability. The absence of nonce checks and the presence of unsanitized paths, even if not yet exploited, amplify this risk. The plugin's clean vulnerability history is a positive indicator, but it does not negate the immediate risks posed by the current code's exposed entry points.

Key Concerns

  • AJAX handlers without authentication checks
  • Flows with unsanitized paths
  • Nonce checks missing on AJAX handlers
Vulnerabilities
None known

Finsbury Media Cookie Consent Security Vulnerabilities

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

Finsbury Media Cookie Consent Code Analysis

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

Output Escaping

89% escaped9 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
finsmeco_serve_asset_handler (asset.php:5)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

Finsbury Media Cookie Consent Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_finsmeco_serve_assetasset.php:36
noprivwp_ajax_finsmeco_serve_assetasset.php:37
WordPress Hooks 4
actionadmin_menuadmin-settings.php:15
actionadmin_initadmin-settings.php:28
actionwp_enqueue_scriptsfinsbury-media-cookie-consent.php:125
actionwp_headfinsbury-media-cookie-consent.php:126
Maintenance & Trust

Finsbury Media Cookie Consent Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedUnknown
PHP min version8.0
Downloads399

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Finsbury Media Cookie Consent Developer Profile

Finsbury Media

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 Finsbury Media Cookie Consent

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

Asset Fingerprints

Script Paths
/wp-content/plugins/finsbury-media-cookie-consent/assets/js/cc-core.js/wp-content/plugins/finsbury-media-cookie-consent/assets/js/cc-setup.js
Version Parameters
finsbury-media-cookie-consent-core-css?ver=1.2.2finsbury-media-cookie-consent-core-js?ver=1.2.2finsbury-media-cookie-consent-setup-css?ver=1.2.2finsbury-media-cookie-consent-setup-js?ver=1.2.2action=finsmeco_serve_asset&f=cc-core.css&ver=1.2.2action=finsmeco_serve_asset&f=cc-setup.css&ver=1.2.2action=finsmeco_serve_asset&f=cc-core.js&ver=1.2.2action=finsmeco_serve_asset&f=cc-setup.js&ver=1.2.2

HTML / DOM Fingerprints

JS Globals
FINSMECOdataLayergtaguetqclarity
FAQ

Frequently Asked Questions about Finsbury Media Cookie Consent