# CVE-2025-50002: WordPress Energia theme <= 1.1.2 - Arbitrary File Upload vulnerability

> An attacker can upload a malicious web shell to the server, leading to remote code execution on sites using the Energia theme.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4gfm-jw9m-ghx4

## What is CVE-2025-50002?

CVE-2025-50002 is a critical vulnerability in Farost Energia, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Farost Energia energia allows Upload a Web Shell to a Web Server.This issue affects Energia: from n/a through <= 1.1.2.

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

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


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

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

## Is CVE-2025-50002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50002 is a critical vulnerability in Farost Energia, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50002 in the wild and no public exploit code.

Affected product: Farost Energia. 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-50002/ (Markdown: https://insights.sbomify.com/CVE-2025-50002/index.md)
```

## Sources

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

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