# CVE-2022-47595: WordPress WP Google Maps Plugin <= 9.0.15 is vulnerable to Path Traversal

> Attackers can exploit a path traversal flaw in the WP Go Maps plugin to read arbitrary files from the server.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-2644-jxq3-c5rc

## What is CVE-2022-47595?

CVE-2022-47595 is a medium-severity path traversal vulnerability in WP Go Maps (formerly WP Google Maps), published on 14 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP Go Maps (formerly WP Google Maps) plugin <= 9.0.15 versions.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-47595?

It affects 1 product.


Products: Codecabin Wp Go Maps.

## How do I fix CVE-2022-47595?

No fix has been published for CVE-2022-47595 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-47595 being exploited?

There is no known exploitation of CVE-2022-47595 in the wild and no public exploit code.

## Other vulnerabilities in WP Go Maps (formerly WP Google Maps)

- [CVE-2019-10692](https://insights.sbomify.com/CVE-2019-10692/): SQL injection in n/a (critical 9.8)
- [CVE-2024-29931](https://insights.sbomify.com/CVE-2024-29931/): WordPress WP Go Maps plugin <= 9.0.29 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-5994](https://insights.sbomify.com/CVE-2024-5994/): WP Go Maps (formerly WP Google Maps) <= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2024-3557](https://insights.sbomify.com/CVE-2024-3557/): WP Go Maps (formerly WP Google Maps) <= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 6.4)
- [CVE-2024-1582](https://insights.sbomify.com/CVE-2024-1582/): WP Go Maps (formerly WP Google Maps) <= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47595 and fix it if it is affected.

What it is: CVE-2022-47595 is a medium-severity path traversal vulnerability in WP Go Maps (formerly WP Google Maps), published on 14 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47595 in the wild and no public exploit code.

Affected product: WP Go Maps (formerly WP Google Maps). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-47595/ (Markdown: https://insights.sbomify.com/CVE-2022-47595/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47595
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47595
- OSV: https://osv.dev/vulnerability/CVE-2022-47595

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47595/
Summaries are generated and may contain mistakes; the official description above is the record.