# CVE-2025-67427: evershop allows unauthenticated attackers to force server to initiate HTTP request via "GET /images" API

> Unauthenticated attackers can force the server to make arbitrary HTTP requests via the images API, potentially accessing internal networks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-vp8w-wj4m-3r7j

## What is CVE-2025-67427?

CVE-2025-67427 is a medium-severity server-side request forgery vulnerability in n/a, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Blind Server-Side Request Forgery (SSRF) vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to force the server to initiate an HTTP request via the "GET /images" API. The vulnerability occurs due to insufficient validation of the "src" query parameter, which permits arbitrary HTTP or HTTPS URIs, resulting in unexpected requests against internal and external networks.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@evershop/evershop` | npm | All versions to 2.1.0 | None |
| `@evershop/evershop` | npm | All versions to 2.1.0 | None |

Products: Evershop Evershop.

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

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

## Is CVE-2025-67427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-28213](https://insights.sbomify.com/CVE-2026-28213/): EverShop Vulnerable to Arbitrary Customer Account Takeover via Exposure of Password Reset Token in API Response (critical 9.8)
- [CVE-2023-46498](https://insights.sbomify.com/CVE-2023-46498/): Code execution in evershop (critical 9.8)
- [CVE-2026-25993](https://insights.sbomify.com/CVE-2026-25993/): EverShop has a Second-Order SQL Injection in URL Rewrite Processing Derived from Category URL Keys (critical 9.3)
- [CVE-2023-46943](https://insights.sbomify.com/CVE-2023-46943/): EverShop at risk to unauthorized access via weak HMAC secret (critical 9.1)
- [CVE-2023-46496](https://insights.sbomify.com/CVE-2023-46496/): Directory Traversal in evershop (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67427 is a medium-severity server-side request forgery vulnerability in n/a, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67427 in the wild and no public exploit code.

Affected packages and fixed versions:
- @evershop/evershop (npm): affected all versions up to 2.1.0; no fix listed
- @evershop/evershop (npm): affected all versions up to 2.1.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-67427/ (Markdown: https://insights.sbomify.com/CVE-2025-67427/index.md)
```

## Sources

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

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