WP Maps · Security record
Is WP Maps safe?
No known vulnerability affects the current version (5.0.3). 35 issues were found in earlier versions and fixed, the latest disclosed on Sep 24, 2026.
Checked 5 days ago against the WPVulnerability database, for version 5.0.3.
How it’s looked after
- Last release
- Oct 28, 2026 (1 week ago)
- Releases in the last year
- 16
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 2 threads in two months
- Active installs
- 60K+
35 known vulnerabilities
- 1 critical
- 9 high
- 12 medium
- 1 low
- 12 not rated
None affects the current version.
Disclosed each year
- 20155
- 20161
- 20181
- 20192
- 20202
- 20221
- 20232
- 20241
- 20254
- 202614
Every known vulnerability in WP Maps
Newest first, with any that affect the current version at the top.
Fixed in 5.0.0 · CVE-2026-13179 · Sep 24, 2026 · Wordfence
Fixed in 5.0.0 · CVE-2026-13456 · Sep 24, 2026 · Wordfence
Fixed in 5.0.0 · CVE-2026-66618 · Aug 21, 2026 · Wordfence
Fixed in 4.9.8 · CVE-2026-18466 · Aug 19, 2026 · Wordfence
Fixed in 4.9.7 · CVE-2026-16265 · Aug 7, 2026 · CVE
Fixed in 4.9.7 · CVE-2026-16263 · Aug 3, 2026 · Wordfence
Fixed in 4.9.7 · CVE-2026-28144 · Jul 31, 2026 · Wordfence
Fixed in 4.9.5 · CVE-2026-9594 · Jun 5, 2026 · Wordfence
Fixed in 4.9.3 · CVE-2026-6381 · May 18, 2026 · Wordfence
Fixed in 4.8.8 · CVE-2025-13364 · Apr 15, 2026 · Wordfence
- critical
Unauthenticated SQL Injection
Fixed in 4.9.2 · CVE-2026-39492 · Apr 8, 2026 · Wordfence
Fixed in 4.9.2 · CVE-2026-2580 · Mar 22, 2026 · Wordfence
Fixed in 4.9.2 · CVE-2026-3222 · Mar 10, 2026 · Wordfence
Fixed in 4.8.7 · CVE-2025-12062 · Feb 16, 2026 · Wordfence
Fixed in 4.8.7 · CVE-2025-67535 · Nov 2, 2025 · Wordfence
Fixed in 4.7.2 · CVE-2025-3504 · Apr 10, 2025 · Wordfence
Fixed in 4.7.2 · CVE-2025-3503 · Apr 10, 2025 · Wordfence
Fixed in 4.7.2 · CVE-2025-3502 · Apr 10, 2025 · Wordfence
Fixed in 4.6.2 · CVE-2024-2386 · Jun 28, 2024 · Wordfence
Fixed in 4.4.3 · CVE-2023-28172 · Mar 13, 2023 · Wordfence
Fixed in 4.4.0 · CVE-2023-23878 · Jan 20, 2023 · Wordfence
Fixed in 4.4.3 · CVE-2022-25600 · Feb 22, 2022 · Wordfence
Fixed in 4.1.4 · Nov 25, 2020 · Patchstack
Fixed in 4.1.5 · CVE-2021-24130 · Nov 25, 2020 · Wordfence
Fixed in 4.1.0 · Sep 21, 2019 · Wordfence
Fixed in 4.1.0 · Sep 21, 2019 · Wordfence
- medium
Cross-Site Scripting
Fixed in 4.0.4 · CVE-2018-0577 · Apr 27, 2018 · Wordfence
- medium
Cross-Site Scripting
Fixed in 3.1.2 · CVE-2016-10878 · Jul 27, 2016 · Wordfence
Fixed in 2.3.10 · CVE-2015-9308 · Aug 21, 2015 · Wordfence
Fixed in 2.3.10 · CVE-2015-9307 · Aug 21, 2015 · Wordfence
Fixed in 2.3.10 · CVE-2015-9309 · Aug 21, 2015 · Wordfence
Fixed in 3.0.0 · Aug 20, 2015 · Wordfence
Fixed in 2.3.7 · CVE-2015-9305 · Apr 24, 2015 · Wordfence
Fixed in 3.0.0 · WPScan
Fixed in 4.1.0 · WPScan
Questions about WP Maps’s security
Is WP Maps safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WP Maps updated: most attacks target sites that haven’t updated.
Does WP Maps have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 35 older issues, fixed in earlier versions, so keep WP Maps up to date.
Is WP Maps still maintained?
Yes. Its last release was 1 week ago. Its authors resolved 1 of the 2 support threads opened in the last two months.
Is WP Maps compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
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.