Placemarks Security & Risk Analysis

wordpress.org/plugins/placemarks

Allow authors to easily manage placemarks and embed custom maps.

20 active installs v3.0.1 PHP + WP 3.0+ Updated Oct 13, 2019
mapmapsplacemarkplacemarksplaces
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Placemarks Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The "placemarks" plugin version 3.0.1 presents a generally good security posture with no known vulnerabilities in its history and a limited attack surface. The static analysis indicates no critical or high-severity taint flows, no dangerous functions, and no file operations or external HTTP requests, which are positive indicators. The presence of capability checks suggests some level of access control is implemented.

However, there are notable areas of concern. A significant weakness lies in the handling of SQL queries; the single SQL query identified is not using prepared statements, which is a substantial risk for SQL injection vulnerabilities. Furthermore, the output escaping is notably poor, with only 18% of outputs properly escaped. This, combined with the absence of nonce checks, significantly increases the risk of Cross-Site Scripting (XSS) vulnerabilities, especially given the presence of a shortcode which can be a vector for injecting malicious content.

Overall, while the plugin benefits from a clean vulnerability history and a contained attack surface, the lack of prepared statements for SQL queries and the low percentage of properly escaped output represent critical security flaws that demand immediate attention. The absence of nonce checks further exacerbates the XSS risk.

Key Concerns

  • SQL queries not using prepared statements
  • Low percentage of properly escaped output
  • No nonce checks
Vulnerabilities
None known

Placemarks Security Vulnerabilities

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

Placemarks Code Analysis

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

SQL Query Safety

0% prepared1 total queries

Output Escaping

18% escaped17 total outputs
Attack Surface

Placemarks Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[placemarks] includes\class-placemarks.php:202
WordPress Hooks 17
actionplugins_loadedincludes\class-placemarks.php:142
actionadmin_enqueue_scriptsincludes\class-placemarks.php:157
actionadmin_enqueue_scriptsincludes\class-placemarks.php:158
actioninitincludes\class-placemarks.php:162
actionadmin_initincludes\class-placemarks.php:165
actionsave_postincludes\class-placemarks.php:166
actionmanage_edit-placemark_columnsincludes\class-placemarks.php:170
actionmanage_posts_custom_columnincludes\class-placemarks.php:171
actionmanage_edit-placemark_sortable_columnsincludes\class-placemarks.php:172
actionpre_get_postsincludes\class-placemarks.php:173
actionrest_api_initincludes\class-placemarks.php:177
actionadmin_initincludes\class-placemarks.php:181
actionadmin_menuincludes\class-placemarks.php:182
actionnetwork_admin_menuincludes\class-placemarks.php:183
actionnetwork_admin_edit_placemarks_optionsincludes\class-placemarks.php:184
actionwp_enqueue_scriptsincludes\class-placemarks.php:200
actionwp_enqueue_scriptsincludes\class-placemarks.php:201
Maintenance & Trust

Placemarks Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedOct 13, 2019
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

Placemarks Developer Profile

Nagmay

5 plugins · 250 total installs

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

How We Detect Placemarks

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/placemarks/vendor/leaflet/leaflet.css/wp-content/plugins/placemarks/admin/css/placemarks-admin.css/wp-content/plugins/placemarks/public/js/placemarks-public.js/wp-content/plugins/placemarks/vendor/leaflet/leaflet.js/wp-content/plugins/placemarks/public/js/includes/overlay-layer.obj.js/wp-content/plugins/placemarks/admin/js/placemarks-admin.js
Script Paths
/wp-content/plugins/placemarks/public/js/placemarks-public.js/wp-content/plugins/placemarks/vendor/leaflet/leaflet.js/wp-content/plugins/placemarks/public/js/includes/overlay-layer.obj.js/wp-content/plugins/placemarks/admin/js/placemarks-admin.js
Version Parameters
/wp-content/plugins/placemarks/vendor/leaflet/leaflet.css?ver=/wp-content/plugins/placemarks/admin/css/placemarks-admin.css?ver=/wp-content/plugins/placemarks/public/js/placemarks-public.js?ver=/wp-content/plugins/placemarks/vendor/leaflet/leaflet.js?ver=/wp-content/plugins/placemarks/public/js/includes/overlay-layer.obj.js?ver=/wp-content/plugins/placemarks/admin/js/placemarks-admin.js?ver=

HTML / DOM Fingerprints

Data Attributes
placemarks-latplacemarks-lngplacemarks-locationplacemarks-locationsplacemarks-typeplacemarks-title+2 more
JS Globals
jsonp_tilesjsonp_locationsjsonp_types
REST Endpoints
/placemarks/v2/settings
FAQ

Frequently Asked Questions about Placemarks