# CVE-2025-9115: Etsy Shop < 3.0.7 - Reflected XSS via $_SERVER['REQUEST_URI']

> Reflected XSS in Etsy Shop plugin allows attackers to execute scripts in victim browsers via unescaped request URI.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-vcp8-mq8x-mxp7

## What is CVE-2025-9115?

CVE-2025-9115 is a medium-severity cross-site scripting vulnerability in Unknown Etsy Shop, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Etsy Shop WordPress plugin before 3.0.7 does not escape the $_SERVER['REQUEST_URI'] parameter before outputting it back in an attribute, which could lead to Reflected Cross-Site Scripting in old web browsers.

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


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

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

## Is CVE-2025-9115 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9115 is a medium-severity cross-site scripting vulnerability in Unknown Etsy Shop, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9115 exists.

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

## Sources

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

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