# CVE-2026-6249: Vvveb CMS 1.0.8.2 Remote Code Execution via Media Upload

> Authenticated attackers can execute arbitrary code by uploading a PHP webshell with a .phtml extension, bypassing extension restrictions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 20 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-7x75-92hx-vr86

## What is CVE-2026-6249?

CVE-2026-6249 is a high-severity vulnerability in Vvveb CMS, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb CMS 1.0.8.2 contains a remote code execution vulnerability in its media upload handler that allows authenticated attackers to execute arbitrary operating system commands by uploading a PHP webshell with a .phtml extension. Attackers can bypass the extension deny-list and upload malicious files to the publicly accessible media directory, then request the file over HTTP to achieve full server compromise.

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

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


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

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

## Is CVE-2026-6249 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6249 is a high-severity vulnerability in Vvveb CMS, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6249 in the wild and no public exploit code.

Affected product: Vvveb CMS. 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-6249/ (Markdown: https://insights.sbomify.com/CVE-2026-6249/index.md)
```

## Sources

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

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