CVE-2023-25039 is a medium severity missing authorization flaw (CVSS 4.3) in the Google Maps CP WordPress plugin, affecting every version through 1.0.43. We could not confirm a fixed version, so check the plugin page for a release newer than 1.0.43. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.
What's affected
- Google Maps CP plugin, all versions up to and including 1.0.43, per the record and the Patchstack listing.
- Fixed version: we could not confirm one, so check the plugin page for a release newer than 1.0.43.
- Severity: CVSS 3.1 score 4.3 Medium, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
Patchstack returned an access denied response to our fetch, so the fixed version is not confirmed here.
How to check if you're exposed
If you manage the site with WP-CLI, list the plugin and its version:
wp plugin list --fields=name,version,status | grep -i codepeople-post-map
The plugin directory slug is codepeople-post-map. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the Google Maps CP entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.
What to do now
- Find every WordPress site that has Google Maps CP installed, including staging copies, and read the version.
- Look for a newer release on the plugin page. If none exists, deactivate the plugin or replace it with a maintained alternative.
- If you cannot update right away, deactivate the plugin until you can.
- Review web server logs for unexpected requests to the plugin around the time you learned of the issue.
Why it matters
The weakness is missing authorization (CWE-862 (Missing Authorization)). Broken access control means a function runs without checking that the caller is allowed to use it. WordPress plugins register many actions that requests can reach, so each one needs an explicit capability check. When the check is missing, the plugin trusts the request, whatever role the requester holds.
The Patchstack listing title refers to feedback submission, so the missing check sits on the plugin's feedback function. The vector needs a low privilege account and shows a low integrity impact, which gives the Medium score of 4.3. The practical effect is limited, but unneeded plugin features are easy to remove. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
It helps to treat plugins like any other dependency. Keep a list of what is installed, which version, and who owns the site. Remove plugins you no longer use, since a deactivated plugin still sits on disk and some of its files may remain reachable.
Quick check
What does the missing check allow?
Per the Patchstack title, feedback submission. The vector shows a low integrity impact and no confidentiality or availability impact.
Why no fixed version?
Patchstack blocked our fetch, and the record only says through 1.0.43. Check the plugin page.
Sources
Last reviewed: 19 October 2026.