CVE-2026-27759: Featured Image from Content < 1.7 Authenticated SSRF via save_post
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.
Security readout for executives and security teams
Plain-English summary
This is a medium-risk WordPress plugin issue. A logged-in Author user could make the site fetch internal HTTP resources and save retrieved content into web-accessible uploads. The main concern is data exposure from internal services, not full site takeover based on the supplied sources.
Executive priority
Prioritize remediation on public WordPress sites where Authors can publish or edit content. This is not described as actively exploited, but it can expose internal data and should be handled in the normal vulnerability patch cycle.
Technical view
Featured Image from Content versions before 1.7 have authenticated SSRF in save_post due to insecure URL fetching combined with file write behavior. The CVSS v4 score is 5.3 with low attack complexity, low privileges required, no user interaction, and limited integrity/scope impacts.
Likely exposure
Exposure is likely limited to WordPress sites running Featured Image from Content before 1.7, especially where Author-level accounts are numerous, externally managed, or weakly controlled. The source bundle provides no CPEs, so plugin inventory is the practical exposure check.
Exploitation context
The sources describe an authenticated Author-level attack path. The CVE is not listed as KEV, and the supplied sources do not state active exploitation in the wild. Treat exploitation status as unconfirmed.
Researcher notes
The key control question is whether authenticated Authors can influence plugin URL fetching during post save. Validate exposure by version and role model first. Avoid assuming broader unauthenticated impact or known exploitation because the provided sources do not support that.
Mitigation direction
Update Featured Image from Content to version 1.7 or later.
Remove the plugin if it is not required.
Limit Author-level access to trusted users only.
Review vendor and WordPress plugin guidance for current remediation details.
Monitor uploads directories for unexpected files from plugin activity.
Validation and detection
Inventory WordPress sites for Featured Image from Content installations.
Confirm installed plugin versions are 1.7 or later.
Review users with Author-level or higher permissions.
Check web-accessible uploads for unexpected internally sourced content.
Review server logs for unusual internal HTTP fetch activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.