# CVE-2025-2279: Maps - Google Maps <= 1.0.6 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via shortcode attributes in the Maps plugin, leading to stored XSS attacks on WordPress sites.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-pg7p-xxvc-73xx

## What is CVE-2025-2279?

CVE-2025-2279 is a medium-severity cross-site scripting vulnerability in Unknown Maps, published on 4 Apr 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Maps  WordPress plugin through 1.0.6 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-2279?

It affects 1 product.


Products: Robosoft Maps.

## How do I fix CVE-2025-2279?

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

## Is CVE-2025-2279 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2279 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2279 and fix it if it is affected.

What it is: CVE-2025-2279 is a medium-severity cross-site scripting vulnerability in Unknown Maps, published on 4 Apr 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2279 exists.

Affected product: Unknown 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-2025-2279/ (Markdown: https://insights.sbomify.com/CVE-2025-2279/index.md)
```

## Sources

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

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