API key overwrite via forged administrator request
Published Jun 15, 2022 · Updated Apr 28, 2026
Cross-site request forgery in AyeCode Ltd API KEY for Google Maps 1.2.1 and earlier allows remote attackers to change the stored API key. The plugin's settings update handler accepts a forged API-key change without verifying request intent or the manage_options capability. Exploitation requires an authenticated administrator to interact with attacker-controlled content, after which affected Google Maps integrations use the attacker-selected key.
Summary
What happened
Cross-site request forgery in AyeCode Ltd API KEY for Google Maps 1.2.1 and earlier allows remote attackers to change the stored API key. The plugin's settings update handler accepts a forged API-key change without verifying request intent or the manage_options capability. Exploitation requires an authenticated administrator to interact with attacker-controlled content, after which affected Google Maps integrations use the attacker-selected key.
The record
- CVE
- CVE-2022-29453
- Published
- Jun 15, 2022
- Updated
- Apr 28, 2026
- Vendor
- AyeCode Ltd
- Product
- API KEY for Google Maps
- Classifications
- CWE-352, CAPEC-62, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.2.1 <=1.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo