# CVE-2026-49849: xShop: Unrestricted File Upload in File Attachment Module in Admin panel leads to Arbitrary Code Execution

> An authenticated administrator can upload malicious PHP files to achieve remote code execution and full system compromise.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-fc35-qjg3-f6g7

## What is CVE-2026-49849?

CVE-2026-49849 is a critical vulnerability in 4xmen xshop, published on 21 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

xShop is an open-source shop developed in Laravel. An Unrestricted File Upload vulnerability in xShop version 3.0.3 allows an authenticated administrator to upload executable files (e.g., .php). By uploading a specially crafted php file, an attacker can achieve Remote Code Execution (RCE) on the server, leading to a full system compromise. Version 3.0.4 fixes the issue.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-49849?


## How do I fix CVE-2026-49849?

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

## Is CVE-2026-49849 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49849 and fix it if it is affected.

What it is: CVE-2026-49849 is a critical vulnerability in 4xmen xshop, published on 21 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49849 exists.

Affected product: 4xmen xshop. 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-2026-49849/ (Markdown: https://insights.sbomify.com/CVE-2026-49849/index.md)
```

## Sources

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

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