# CVE-2018-25437: WordPress CherryFramework Themes 3.1.4 Backup File Download

> Unauthenticated attackers can download sensitive backup files containing theme contents via an unprotected endpoint in CherryFramework Themes.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-79qh-whpm-vxr5

## What is CVE-2018-25437?

CVE-2018-25437 is a high-severity missing authorization vulnerability in Cherryframework Cherry Framework Themes, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress CherryFramework Themes 3.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to download sensitive backup files by accessing the download_backup.php endpoint. Attackers can directly access the download_backup.php script in the admin/data_management directory to obtain ZIP archives containing the entire wp-content/themes directory contents.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-25437?


## How do I fix CVE-2018-25437?

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

## Is CVE-2018-25437 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25437 and fix it if it is affected.

What it is: CVE-2018-25437 is a high-severity missing authorization vulnerability in Cherryframework Cherry Framework Themes, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25437 exists.

Affected product: Cherryframework Cherry Framework Themes. 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-2018-25437/ (Markdown: https://insights.sbomify.com/CVE-2018-25437/index.md)
```

## Sources

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

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