Custom Referral Spam Blocker Security & Risk Analysis

wordpress.org/plugins/custom-referral-spam-blocker

Custom Referral Spam Blocker gives you the control to ensure that dishonest referral sources are blocked from Google Analytics.

300 active installs v1.4.6 PHP + WP 3.0.1+ Updated Feb 9, 2017
referral-spamreferralsseospam
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Custom Referral Spam Blocker Safe to Use in 2026?

Generally Safe

Score 85/100

Custom Referral Spam Blocker has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The plugin 'custom-referral-spam-blocker' v1.4.6 exhibits a generally good security posture, with no known critical or high-severity vulnerabilities in its history and a strong adherence to secure coding practices regarding SQL queries. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the attack surface, which is a positive indicator. However, the static analysis reveals some areas of concern that temper this positive outlook. Notably, the presence of unsanitized paths in the taint analysis, despite not reaching critical or high severity, suggests a potential for unintended file access or manipulation if exploited. Furthermore, the output escaping is only 52% proper, indicating a risk of cross-site scripting (XSS) vulnerabilities, especially if dynamic content is being outputted without sufficient sanitization. The file operations and external HTTP requests, while not inherently vulnerable, are entry points that require careful monitoring and secure implementation. Given the lack of historical vulnerabilities, it appears the developers have a generally good track record, but the static analysis flags specific areas for improvement to ensure a robust security posture.

Key Concerns

  • Unsanitized paths found in taint analysis
  • Low percentage of properly escaped output
  • No capability checks found
  • No nonce checks found
Vulnerabilities
None known

Custom Referral Spam Blocker Security Vulnerabilities

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

Custom Referral Spam Blocker Code Analysis

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

Output Escaping

52% escaped21 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<example> (idna-convert\example.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Custom Referral Spam Blocker Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actioninitcustom-referral-spam-blocker.php:61
actionnetwork_admin_menucustom-referral-spam-blocker.php:69
actionadmin_menucustom-referral-spam-blocker.php:72
actionadmin_initcustom-referral-spam-blocker.php:75
filterhttp_request_timeoutcustom-referral-spam-blocker.php:156
actionnetwork_admin_edit_csrb_network_admin_settings_postcustom-referral-spam-blocker.php:202
actionplugins_loadedcustom-referral-spam-blocker.php:278
actionplugins_loadedcustom-referral-spam-blocker.php:328
Maintenance & Trust

Custom Referral Spam Blocker Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedFeb 9, 2017
PHP min version
Downloads17K

Community Trust

Rating80/100
Number of ratings10
Active installs300
Developer Profile

Custom Referral Spam Blocker Developer Profile

csmicfool

2 plugins · 310 total installs

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

How We Detect Custom Referral Spam Blocker

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Custom Referral Spam Blocker