Security readout for executives and security teams
Plain-English summary
This issue could let an outside attacker trick a WordPress user into unintentionally deleting map data, deleting marker categories, or copying maps in the WP Google Map plugin. It is not reported as actively exploited in the provided sources, but exposed sites using version 4.2.3 or older should treat it as a routine security update priority.
Executive priority
Handle as moderate priority. This is not a known mass-exploitation emergency from the supplied evidence, but it can affect website content integrity and availability. Remediate during the next maintenance cycle, faster for public sites where maps support customer-facing operations.
Technical view
CVE-2022-25600 is a CSRF flaw in Flippercode WP Google Map Plugin versions 4.2.3 and earlier. The affected actions are Delete Marker Category, Delete Map, and Copy Map. CVSS 3.1 is 5.4, with network reachability, low attack complexity, no attacker privileges, required user interaction, and limited integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the WP Google Map Plugin installed at version 4.2.3 or earlier. Business impact is mainly unauthorized changes or deletion of plugin-managed map content if a relevant authenticated WordPress user is induced to trigger the vulnerable action.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. The CVSS vector indicates attacker privileges are not required, but user interaction is required. Because this is CSRF, practical exploitation likely depends on a logged-in WordPress user with access to the affected plugin functions.
Researcher notes
Evidence identifies affected functions and version range, but the bundle does not include detailed root-cause code, proof of concept, or a named fixed release. Avoid assuming exploit maturity. Validate against vendor changelog and Patchstack before closing vulnerability-management tickets.
Mitigation direction
- Inventory WordPress sites for WP Google Map Plugin usage and version.
- Prioritize upgrades for any installation at version 4.2.3 or earlier.
- Check WordPress.org and Patchstack guidance for the fixed version and vendor recommendations.
- Restrict plugin administration access to trusted users until remediation is complete.
- Back up map content before updating or making administrative changes.
Validation and detection
- Confirm the plugin version from WordPress admin or asset inventory.
- Review plugin changelog and Patchstack entry for affected-version confirmation.
- Check recent WordPress admin activity for unexpected map or marker-category changes.
- Verify only authorized roles can access map-management functions.
- Confirm remediation by documenting installed version after update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-25600 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/wp-google-map-plugin/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/wp-google-map-plugin/wordpress-wp-google-map-plugin-4-2-3-cross-site-request-forgery-csrf-vulnerabilityCVE reference · x_refsource_CONFIRM
- FEDORA-2022-4b3079c1beCVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2022-956b6078fbCVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2022-706aac2786CVE reference · vendor-advisory, x_refsource_FEDORA
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.