# CVE-2026-6261: Betheme <= 28.4 - Authenticated (Author+) Arbitrary File Upload to Remote Code Execution via Icon Pack Upload

> Authenticated attackers with author-level access can upload malicious files to achieve remote code execution in the Betheme WordPress theme.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-xjrr-vq8h-v4xh

## What is CVE-2026-6261?

CVE-2026-6261 is a high-severity vulnerability in MuffinGroup Betheme, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Betheme theme for WordPress is vulnerable to Arbitrary File Upload in versions up to, and including, 28.4. This is due to the upload_icons() function workflow moving and unzipping user-controlled ZIP files into a public uploads directory without validating extracted file types. This makes it possible for authenticated attackers, with author-level access and above, to upload arbitrary files (including PHP) and achieve remote code execution via the Icons icon-pack upload flow.

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

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


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

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

## Is CVE-2026-6261 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6261 is a high-severity vulnerability in MuffinGroup Betheme, published on 5 May 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-6261 in the wild and no public exploit code.

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

## Sources

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

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