Basic Google Maps Placemarks · Security record
Is Basic Google Maps Placemarks safe?
No known vulnerability affects the current version (1.10.8). 3 issues were found in earlier versions and fixed, the latest disclosed on Apr 15, 2026.
Checked 1 day ago against the WPVulnerability database, for version 1.10.8.
How it’s looked after
- Last release
- Mar 31, 2026 (7 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Active installs
- 2K+
3 known vulnerabilities
- 1 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20141
- 20261
Every known vulnerability in Basic Google Maps Placemarks
Newest first, with any that affect the current version at the top.
Fixed in 1.10.8 · CVE-2026-3581 · Apr 15, 2026 · Wordfence
Fixed in 1.10.3 · Aug 1, 2014 · Patchstack
Fixed in 1.10.3 · WPScan
Questions about Basic Google Maps Placemarks’s security
Is Basic Google Maps Placemarks safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Basic Google Maps Placemarks updated: most attacks target sites that haven’t updated.
Does Basic Google Maps Placemarks have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep Basic Google Maps Placemarks up to date.
Is Basic Google Maps Placemarks still maintained?
Its last release was 7 months ago. No support threads were opened in the last two months.
Is Basic Google Maps Placemarks compatible with the latest WordPress?
Basic Google Maps Placemarks’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.