Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

Country Blocker for AdSense

by Jesús Rodríguez · Fewer than 10 active installs · Checked 4 Nov 2026
Limited data2 Criticals1 Warning

Limited data: Country Blocker for AdSense has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

39/ 100Limited data
Canary Score

Based on 3 of 5 areas

Capped at 39: a vulnerability has no patch.

Sub-scores for Country Blocker for AdSense
Ownership100
Maintenance0
Security35
SupportNo data
ReputationNo data

How the score works

Active signals

Open issues right now, with links to the source.

  • CriticalSEC-2Vulnerability published 18 Feb 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.4 Mar 2026Evidence
  • CriticalMNT-1No release in 42 months (last release 27 Apr 2023). Plan a replacement if the plugin is important to your site.26 Apr 2024Evidence
  • WarningMNT-2Tested up to WordPress 6.2.15, 9 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

History: 1 past vulnerability, 1 still unpatched in the current version. Patched issues are listed in the Security record, not here.

Quick answers

Is Country Blocker for AdSense still maintained?
No. Last release 27 Apr 2023, over 3 years ago. 27 Apr 2023 · wordpress.org
Who owns Country Blocker for AdSense, and has it changed hands?
No change recorded. 4 Nov 2026 · SVN log
Was Country Blocker for AdSense removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Country Blocker for AdSense safe?
No. 1 known vulnerability has no fix in the current version. 18 Feb 2026 · Wordfence Intelligence
Is the latest Country Blocker for AdSense update safe to install?
Not enough data. No release date on record for the current version. Release history

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
plugin-master27 Apr 2023 to 27 Apr 2023, 1 commits
soyrodriguez27 Apr 2023 to 27 Apr 2023, 1 commits

2 committers recorded. No ownership changes recorded since 2023.

Maintenance

Last release
4 years ago
Releases, 24 months
0
Tested up to
6.2 vs 7.1
Requires PHP
7.4 supported 8.2+

Last release 27 Apr 2023. Tested up to 6.2, 9 major versions behind WordPress 7.1. Release history builds as we see new versions.

Support

Resolved, last 2 months
n/a
Threads, last 2 months
0

Trend appears after 8 weekly snapshots.

Security record

1 vulnerability in 24 months, 1 with no fix in the current version.

DateIssueCVSSAffectedFixed inDays to patch
18 Feb 2026Cross-Site Request Forgery to Settings Update4.3<= 1.0No fixn/a

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
4 star0
3 star0
2 star0
1 star0

Momentum

Active installs
Fewer than 10

Trend appears after 8 weekly snapshots.

Facts

Version
1.0
Author
Jesús Rodríguez
Added
27 Apr 2023
Last updated
27 Apr 2023
Active installs
Fewer than 10
Requires WordPress
5.3
Tested up to
6.2.15
Requires PHP
7.4
Category
not stated
Tags
ads, block, adsense, country

Questions about Country Blocker for AdSense

Is Country Blocker for AdSense still maintained?

No. Last release 27 Apr 2023, over 3 years ago.

Who owns Country Blocker for AdSense, and has it changed hands?

No change recorded.

Was Country Blocker for AdSense removed from wordpress.org?

No. Listed on wordpress.org as of 4 Nov 2026.

Is Country Blocker for AdSense safe?

No. 1 known vulnerability has no fix in the current version.

Is the latest Country Blocker for AdSense update safe to install?

Not enough data. No release date on record for the current version.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 4 Nov 2026.Report a data issue