# CVE-2025-14437: Hummingbird <= 3.18.0 - Unauthenticated Sensitive Information Exposure via Log File

> Unauthenticated attackers can extract sensitive Cloudflare API credentials from log files in the Hummingbird Performance WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r7mg-q5mv-qg2v

## What is CVE-2025-14437?

CVE-2025-14437 is a high-severity vulnerability in wpmudev Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Hummingbird Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.18.0 via the 'request' function. This makes it possible for unauthenticated attackers to extract sensitive data including Cloudflare API credentials.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2025-14437 being exploited?

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

Public exploit code:

- WordPress Hummingbird <= 3.18.0 - Sensitive Information Exposure via Log File (nuclei): http/cves/2025/CVE-2025-14437.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14437 is a high-severity vulnerability in wpmudev Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN, published on 18 Dec 2025. 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-2025-14437 exists.

Affected product: wpmudev Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN. 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-14437/ (Markdown: https://insights.sbomify.com/CVE-2025-14437/index.md)
```

## Sources

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

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