{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14437 exists.","fix":"No fix has been published for CVE-2025-14437 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14437 is a high-severity vulnerability in wpmudev Hummingbird Performance – Cache \u0026 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."},"fix_prompt":"Check this codebase for CVE-2025-14437 and fix it if it is affected.\n\nWhat it is: CVE-2025-14437 is a high-severity vulnerability in wpmudev Hummingbird Performance – Cache \u0026 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14437 exists.\n\nAffected product: wpmudev Hummingbird Performance – Cache \u0026 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-14437/ (Markdown: https://insights.sbomify.com/CVE-2025-14437/index.md)","id":"CVE-2025-14437","markdown":"https://insights.sbomify.com/CVE-2025-14437/index.md","name":"CVE-2025-14437","record":{"aliases":["GHSA-r7mg-q5mv-qg2v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress performance plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract sensitive Cloudflare API credentials from log files in the Hummingbird Performance WordPress plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-14437.yaml","stars":null,"title":"WordPress Hummingbird \u003c= 3.18.0 - Sensitive Information Exposure via Log File"}],"tier":"weaponised"},"has_fix":null,"headline":"Hummingbird \u003c= 3.18.0 - Unauthenticated Sensitive Information Exposure via Log File","id":"CVE-2025-14437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Xagio SEO \u003c= 7.1.0.30 - Authenticated (Subscriber+) Server-Side Request Forgery","id":"CVE-2025-14438"},"packages":[],"prev":{"headline":"Brevo for WooCommerce \u003c= 4.0.49 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2025-14436"},"products":["Hummingbird Performance – Cache \u0026 Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN"],"published":"2025-12-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wpmudev"]},"summary":"Unauthenticated attackers can extract sensitive Cloudflare API credentials from log files in the Hummingbird Performance WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-14437/"}