WP GeoNames Security & Risk Analysis

wordpress.org/plugins/wp-geonames

Allows you to insert all or part of the global GeoNames database in your WordPress base.

200 active installs v1.9.2 PHP 5.3+ WP 3.0.1+ Updated May 2, 2025
citydatageosqltable
99
A · Safe
CVEs total2
Unpatched0
Last CVEDec 11, 2024
Download
Safety Verdict

Is WP GeoNames Safe to Use in 2026?

Generally Safe

Score 99/100

WP GeoNames has a strong security track record. Known vulnerabilities have been patched promptly.

2 known CVEsLast CVE: Dec 11, 2024Updated 11mo ago
Risk Assessment

The wp-geonames plugin v1.9.2 exhibits several security concerns, primarily stemming from a large unprotected attack surface and a lack of robust input sanitization. With 8 out of 10 entry points lacking authentication checks, this plugin is highly susceptible to unauthorized access and potential abuse. The static analysis further highlights critical vulnerabilities with 5 high-severity taint flows that involve unsanitized paths, indicating a significant risk of code injection or other malicious operations. Additionally, the complete absence of prepared statements for SQL queries is a major red flag, exposing the plugin to SQL injection attacks. While the plugin has no currently unpatched CVEs, its history of two medium-severity vulnerabilities, both related to Cross-site Scripting, suggests a recurring pattern of input sanitization weaknesses. The presence of nonce checks and capability checks on some AJAX handlers is a positive sign, but it is overshadowed by the sheer number of unprotected AJAX endpoints. In conclusion, while the plugin does not have critical or high unpatched vulnerabilities at this time, the combination of a wide unprotected attack surface, critical taint flows, and unprevented SQL injection risks presents a substantial security posture that requires immediate attention.

Key Concerns

  • 8 unprotected AJAX handlers
  • 26 SQL queries, 0% prepared
  • 5 critical severity taint flows
  • 20% output properly escaped
  • 2 medium severity CVEs
Vulnerabilities
2

WP GeoNames Security Vulnerabilities

CVEs by Year

2 CVEs in 2024
2024
Patched Has unpatched

Severity Breakdown

Medium
2

2 total CVEs

CVE-2024-11757medium · 6.4Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

WP GeoNames <= 1.9.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Dec 11, 2024 Patched in 1.9.1 (1d)
CVE-2024-53812medium · 6.1Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

WP GeoNames <= 1.8 - Reflected Cross-Site Scripting

Dec 2, 2024 Patched in 1.9 (11d)
Code Analysis
Analyzed Mar 16, 2026

WP GeoNames Code Analysis

Dangerous Functions
0
Raw SQL Queries
26
0 prepared
Unescaped Output
82
21 escaped
Nonce Checks
7
Capability Checks
9
File Operations
16
External Requests
2
Bundled Libraries
0

SQL Query Safety

0% prepared26 total queries

Output Escaping

20% escaped103 total outputs
Data Flows
5 unsanitized

Data Flow Analysis

10 flows5 with unsanitized paths
wpGeonames_admin (inc\wp-geonames_admin.php:106)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
8 unprotected

WP GeoNames Attack Surface

Entry Points10
Unprotected8

AJAX Handlers 9

authwp_ajax_wpgeonamesAjaxinc\wp-geonames_admin.php:93
authwp_ajax_wpgeonameGetCityinc\wp-geonames_admin.php:94
authwp_ajax_wpGeonamesAddCountryinc\wp-geonames_admin.php:95
authwp_ajax_wpGeonamesAddPostalinc\wp-geonames_admin.php:96
noprivwp_ajax_geoDataRegionwp-geonames.php:23
authwp_ajax_geoDataRegionwp-geonames.php:24
noprivwp_ajax_geoDataCitywp-geonames.php:25
authwp_ajax_geoDataCitywp-geonames.php:26
authwp_ajax_wpgeonameGetCitywp-geonames.php:27

Shortcodes 1

[wp-geonames] wp-geonames.php:22
WordPress Hooks 3
actionadmin_enqueue_scriptsinc\wp-geonames_admin.php:97
actionadmin_menuinc\wp-geonames_admin.php:98
actioninitwp-geonames.php:16
Maintenance & Trust

WP GeoNames Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedMay 2, 2025
PHP min version5.3
Downloads16K

Community Trust

Rating100/100
Number of ratings2
Active installs200
Developer Profile

WP GeoNames Developer Profile

Jacques Malgrange

4 plugins · 530 total installs

69
trust score
Avg Security Score
86/100
Avg Patch Time
777 days
View full developer profile
Detection Fingerprints

How We Detect WP GeoNames

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-geonames/leaflet/leaflet.css/wp-content/plugins/wp-geonames/leaflet/leaflet.js

HTML / DOM Fingerprints

JS Globals
wpGeonames
REST Endpoints
/wp-json/wpgeonames/v1/region/wp-json/wpgeonames/v1/city
Shortcode Output
[wp-geonames]
FAQ

Frequently Asked Questions about WP GeoNames