Visitor Maps Extended Referer Field
Limited data: Visitor Maps Extended Referer Field has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Capped at 39: a vulnerability has no patch.
| Ownership | 100 |
|---|---|
| Maintenance | 0 |
| Security | 35 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is Visitor Maps Extended Referer Field still maintained?
- No. Last release 2 Mar 2014, over 12 years ago. 2 Mar 2014 · wordpress.org
- Who owns Visitor Maps Extended Referer Field, and has it changed hands?
- No change recorded. 4 Nov 2026 · SVN log
- Was Visitor Maps Extended Referer Field removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is Visitor Maps Extended Referer Field safe?
- No. 1 known vulnerability has no fix in the current version. 10 Feb 2026 · Wordfence Intelligence
- Is the latest Visitor Maps Extended Referer Field update safe to install?
- No ownership change before 1.2.6. No one-star spike after it. 2 Mar 2014 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 10 Feb 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.24 Feb 2026Evidence
- CriticalMNT-1No release in 154 months (last release 2 Mar 2014). Plan a replacement if the plugin is important to your site.2 Mar 2015Evidence
- WarningMNT-2Tested up to WordPress 3.7.41, 34 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
No ownership change since 2012.
Maintenance
- Last release
- 13 years ago
- Releases, 24 months
- 0
- Tested up to
- 3.7 vs 7.1
- Requires PHP
- not stated supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 2 Mar 2014. Tested up to 3.7, 34 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 3.0.
| 5 star | 1 |
|---|---|
| 4 star | 0 |
| 3 star | 1 |
| 2 star | 0 |
| 1 star | 1 |
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 10 Feb 2026 | Visitor Maps Extended Referer Field <= 1.2.6 - Reflected Cross-Site Scripting | 6.1 | <= 1.2.6 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
100+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | 1.2.6 |
|---|---|
| Author | Hugh Mungus |
| Added | 7 Mar 2012 |
| Last updated | 2 Mar 2014 |
| Active installs | 100+ |
| Requires WordPress | 2.8.4 |
| Tested up to | 3.7.41 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | map, who, maps, whos, visitor |
Questions
Is Visitor Maps Extended Referer Field still maintained?
No. Last release 2 Mar 2014, over 12 years ago.
Who owns Visitor Maps Extended Referer Field, and has it changed hands?
No change recorded.
Was Visitor Maps Extended Referer Field removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is Visitor Maps Extended Referer Field safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest Visitor Maps Extended Referer Field update safe to install?
No ownership change before 1.2.6. No one-star spike after it.