# CVE-2026-27759: Featured Image from Content < 1.7 Authenticated SSRF via save_post

> Authenticated Authors can exploit SSRF in the Featured Image from Content plugin to fetch internal resources and store sensitive data in web-accessible directories.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-pmx8-fmc2-4rjp

## What is CVE-2026-27759?

CVE-2026-27759 is a medium-severity server-side request forgery vulnerability in Dhrumil Kumbhani Featured Image from Content, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Featured Image from Content (featured-image-from-content) WordPress plugin versions prior to 1.7 contain an authenticated server-side request forgery vulnerability that allows Author-level users to fetch internal HTTP resources. Attackers can exploit insecure URL fetching and file write operations to retrieve sensitive internal data and store it in web-accessible upload directories.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-27759?


## How do I fix CVE-2026-27759?

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

## Is CVE-2026-27759 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27759 and fix it if it is affected.

What it is: CVE-2026-27759 is a medium-severity server-side request forgery vulnerability in Dhrumil Kumbhani Featured Image from Content, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27759 in the wild and no public exploit code.

Affected product: Dhrumil Kumbhani Featured Image from Content. 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-2026-27759/ (Markdown: https://insights.sbomify.com/CVE-2026-27759/index.md)
```

## Sources

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

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