API KEY for Google Maps <= 1.2.1 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.2.2
- Affected Plugin
- API KEY for Google Maps
- Affected Version
<= 1.2.1- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-29453
At a glance
CVE-2022-29453 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the API KEY for Google Maps WordPress plugin, affecting versions <= 1.2.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.2; sites on affected versions should update now. Disclosed June 2022.
Vulnerability Overview
Cross-Site Request Forgery (CSRF) vulnerability in API KEY for Google Maps plugin <= 1.2.1 at WordPress leading to Google Maps API key update.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in API KEY for Google Maps <= 1.2.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For API KEY for Google Maps the fix is 1.2.2: builds <= 1.2.1 are affected, anything from 1.2.2 onward is not.
Remediation
Update to version 1.2.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to API KEY for Google Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: API KEY for Google Maps 1.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C