# CVE-2025-28094: ShopXO Vulnerable to Server-Side Request Forgery (SSRF) and Cross-Site Scripting (XSS)

> Attackers can exploit SSRF and XSS flaws in Shopxo to access internal resources or execute scripts in user browsers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-24cf-848g-762c

## What is CVE-2025-28094?

CVE-2025-28094 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

shopxo v6.4.0 has a ssrf/xss vulnerability in multiple places.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including shopxo/shopxo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopxo/shopxo` | Packagist | All versions to 6.4.0 | None |
| `shopxo/shopxo` | Packagist | All versions to 6.4.0 | None |

Products: Shopxo Shopxo.

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

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

## Is CVE-2025-28094 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-26325](https://insights.sbomify.com/CVE-2025-26325/): File upload in n/a (critical 9.8)
- [CVE-2022-28056](https://insights.sbomify.com/CVE-2022-28056/): Incorrect Permission Assignment for Critical Resource in ShopXO (critical 9.8)
- [CVE-2020-19778](https://insights.sbomify.com/CVE-2020-19778/): Privilege escalation in n/a (critical 9.8)
- [CVE-2021-27817](https://insights.sbomify.com/CVE-2021-27817/): ShopXO RCE Vulnerability (critical 9.8)
- [CVE-2019-5886](https://insights.sbomify.com/CVE-2019-5886/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28094 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2025. Any signed-in user can exploit it over the network, 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-28094 exists.

Affected packages and fixed versions:
- shopxo/shopxo (Packagist): affected all versions up to 6.4.0; no fix listed
- shopxo/shopxo (Packagist): affected all versions up to 6.4.0; no fix listed

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

## Sources

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

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