Nearby Places Search Security & Risk Analysis

wordpress.org/plugins/nearby-places-search

Nearby Places Search: This Plugin integrates with the Google Places and GMap.

10 active installs v1 PHP + WP + Updated Jun 15, 2017
admingoogle-map-place-searchgoogle-map-shortcodelocationradius
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Nearby Places Search Safe to Use in 2026?

Generally Safe

Score 85/100

Nearby Places Search has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The "nearby-places-search" v1 plugin exhibits a generally positive security posture based on the provided static analysis. The absence of dangerous functions, external HTTP requests, and file operations, coupled with 100% of SQL queries using prepared statements, indicates a commitment to secure coding practices. The high percentage of properly escaped output (93%) is also commendable, mitigating common cross-site scripting (XSS) risks. The plugin also correctly leverages capability checks for its single entry point, the shortcode.

However, a notable concern is the complete lack of nonce checks. While the static analysis doesn't reveal any direct vulnerabilities from this, it represents a significant gap in protecting against Cross-Site Request Forgery (CSRF) attacks. Any function that modifies data or performs sensitive actions should ideally be protected by nonces. The absence of taint analysis data also means that potential vulnerabilities in complex data flows might have been missed. The vulnerability history being clear of any CVEs is a strong positive, suggesting the plugin has historically been well-maintained and secure, but this cannot entirely compensate for the identified lack of nonce protection.

In conclusion, "nearby-places-search" v1 shows strengths in its handling of SQL and output sanitization, and its minimal attack surface is well-protected by capability checks. The primary area for improvement and a clear security risk is the absence of nonce checks, which should be addressed to prevent potential CSRF vulnerabilities. Without this, the plugin's overall security is good but not excellent.

Key Concerns

  • Missing nonce checks
Vulnerabilities
None known

Nearby Places Search Security Vulnerabilities

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

Nearby Places Search Code Analysis

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

Output Escaping

93% escaped116 total outputs
Attack Surface

Nearby Places Search Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[nearby_places_search_code] plugin.php:24
WordPress Hooks 4
actionwp_enqueue_scriptsplugin.php:40
actionadmin_menuplugin.php:86
actionadmin_initplugin.php:87
actionadmin_enqueue_scriptsplugin.php:231
Maintenance & Trust

Nearby Places Search Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedJun 15, 2017
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Nearby Places Search Developer Profile

Dipankar Biswas

1 plugin · 10 total installs

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

How We Detect Nearby Places Search

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/nearby-places-search/css/nearby_places_search.css/wp-content/plugins/nearby-places-search/js/nearby-place.js
Script Paths
//maps.googleapis.com/maps/api/js
Version Parameters
v=3

HTML / DOM Fingerprints

JS Globals
object_name
Shortcode Output
[nearby_places_search_code]
FAQ

Frequently Asked Questions about Nearby Places Search