# CVE-2025-4868: merikbest ecommerce-spring-reactjs File Upload Endpoint admin path traversal

> Attackers with admin permissions can exploit a path traversal vulnerability in the file upload endpoint to read or modify arbitrary files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-wgg4-4x3x-c77c

## What is CVE-2025-4868?

CVE-2025-4868 is a medium-severity path traversal vulnerability in merikbest ecommerce-spring-reactjs, published on 18 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in merikbest ecommerce-spring-reactjs up to 464e610bb11cc2619cf6ce8212ccc2d1fd4277fd. It has been rated as critical. Affected by this issue is some unknown functionality of the file /api/v1/admin/ of the component File Upload Endpoint. The manipulation of the argument filename leads to path traversal. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-4868 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4868 is a medium-severity path traversal vulnerability in merikbest ecommerce-spring-reactjs, published on 18 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4868 exists.

Affected product: merikbest ecommerce-spring-reactjs. 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-4868/ (Markdown: https://insights.sbomify.com/CVE-2025-4868/index.md)
```

## Sources

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

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