# CVE-2023-46498: Code execution in evershop

> Remote attackers can execute arbitrary code and read sensitive data via the deleteCustomer route in EverShop.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5mmr-9qx3-3pf9

## What is CVE-2023-46498?

CVE-2023-46498 is a critical code injection vulnerability in n/a, published on 8 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information and execute arbitrary code via the /deleteCustomer/route.json file.

## Which versions are affected by CVE-2023-46498?

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 | 1.0.0-rc.8 |
| `@evershop/evershop` | npm | All versions | 1.0.0-rc.8 |

Products: Evershop Evershop.

## How do I fix CVE-2023-46498?

Upgrade @evershop/evershop to 1.0.0-rc.8 or later.

## Is CVE-2023-46498 being exploited?

There is no known exploitation of CVE-2023-46498 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-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)
- [CVE-2025-67419](https://insights.sbomify.com/CVE-2025-67419/): evershop allows unauthenticated attackers to exhaust application server's resources via "GET /images" API (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46498 and fix it if it is affected.

What it is: CVE-2023-46498 is a critical code injection vulnerability in n/a, published on 8 Dec 2023. 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-2023-46498 in the wild and no public exploit code.

Affected packages and fixed versions:
- @evershop/evershop (npm): affected all versions; fixed in 1.0.0-rc.8
- @evershop/evershop (npm): affected all versions; fixed in 1.0.0-rc.8

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

## Sources

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

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