Security readout for executives and security teams
Plain-English summary
This issue lets an attacker trick a logged-in WordPress user into changing the Google Maps API key used by the API KEY for Google Maps plugin. The business impact is limited but real: maps may break, usage could shift to an attacker-controlled key, and site integrity is affected.
Executive priority
Treat this as a routine but time-bound remediation item. It is not listed as known exploited in the supplied data, but affected public WordPress sites should be reviewed because the issue can alter site configuration and disrupt Google Maps functionality.
Technical view
CVE-2022-29453 is a CWE-352 CSRF flaw in AyeCode Ltd API KEY for Google Maps for WordPress versions <= 1.2.1. CVSS 3.1 is 5.4, with network reachability, low complexity, no attacker privileges, required user interaction, low integrity impact, and low availability impact.
Likely exposure
Exposure is limited to WordPress sites with the API KEY for Google Maps plugin installed at version 1.2.1 or earlier. Risk depends on whether a privileged WordPress user can be induced to interact with attacker-controlled content while authenticated.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The vulnerability requires user interaction and affects a configuration update path, so opportunistic mass impact is less likely than targeted abuse against WordPress administrators.
Researcher notes
Focus validation on the plugin settings update workflow and whether CSRF protections prevent unauthorized API key changes. The bundle does not provide a fixed version, patch details, exploit evidence, or proof-of-concept information, so remediation should reference current vendor and Patchstack guidance.
Mitigation direction
- Inventory WordPress sites for the API KEY for Google Maps plugin.
- Check installed plugin versions and flag version 1.2.1 or earlier.
- Review the WordPress plugin page and Patchstack entry for vendor update guidance.
- Update, disable, or remove the plugin based on vendor guidance.
- Restrict administrative sessions and reinforce CSRF protections through standard WordPress hardening.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record the installed plugin version from WordPress administration or asset inventory.
- Review whether Google Maps API key settings changed unexpectedly.
- Check access and audit logs around plugin settings changes.
- Verify remediation against vendor or Patchstack guidance after changes.
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-29453 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/api-key-for-google-maps/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/api-key-for-google-maps/wordpress-api-key-for-google-maps-plugin-1-2-1-csrf-vulnerability-leading-to-google-maps-api-key-updateCVE reference · x_refsource_CONFIRM
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.