# CVE-2025-9985: Featured Image from URL (FIFU) <= 5.2.7 - Unauthenticated Information Exposure via Log File

> Unauthenticated attackers can view sensitive information via publicly exposed log files in the Featured Image from URL WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 26 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-456r-h9vm-xcmj

## What is CVE-2025-9985?

CVE-2025-9985 is a medium-severity vulnerability in marceljm Featured Image from URL (FIFU), published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Featured Image from URL (FIFU) plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.2.7 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log files.

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

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


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

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

## Is CVE-2025-9985 being exploited?

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

Public exploit code:

- Featured Image from URL (FIFU) <= 5.2.7 - Unauthenticated Information Exposure via Log File (nuclei): http/cves/2025/CVE-2025-9985.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9985 is a medium-severity vulnerability in marceljm Featured Image from URL (FIFU), published on 26 Sep 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-9985 exists.

Affected product: marceljm Featured Image from URL (FIFU). 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-9985/ (Markdown: https://insights.sbomify.com/CVE-2025-9985/index.md)
```

## Sources

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

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