# CVE-2025-12637: Elastic Theme Editor <= 0.0.3 - Authenticated (Subscriber+) Arbitrary File Upload

> Authenticated attackers can upload arbitrary files via a dynamic code generation feature, potentially leading to remote code execution on the server.

- **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:** 11 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fx5w-2jmg-j2wm

## What is CVE-2025-12637?

CVE-2025-12637 is a high-severity vulnerability in koopersmith Elastic Theme Editor, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Elastic Theme Editor plugin for WordPress is vulnerable to arbitrary file uploads due to a dynamic code generation feature in the process_theme function in all versions up to, and including, 0.0.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-12637 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12637 is a high-severity vulnerability in koopersmith Elastic Theme Editor, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12637 in the wild and no public exploit code.

Affected product: koopersmith Elastic Theme Editor. 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-12637/ (Markdown: https://insights.sbomify.com/CVE-2025-12637/index.md)
```

## Sources

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

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