dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-27759

MEDIUM · 5.3 CVSS v4.0 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The featured-image-from-content WordPress plugin versions before 1.7 contains an authenticated server-side request forgery (SSRF) vulnerability. Attackers with Author-level privileges can exploit insecure URL fetching to make the server request internal HTTP resources (such as localhost, intranet endpoints, or cloud metadata services) and write the retrieved sensitive data to web-accessible upload directories.

MitigationUpdate the featured-image-from-content plugin to version 1.7 or later, which patches the insecure URL fetching functionality. Additionally, restrict Author-level user permissions and monitor for suspicious internal resource requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'featured-image-from-content' in the installed plugins list
    Affected if The plugin appears in the installed plugins list and is activated
  2. Check the installed plugin version
    Click on the plugin in the WordPress plugins list or check the plugin header in wp-content/plugins/featured-image-from-content/featured-image-from-content.php for the Version comment
    Affected if The installed version is below 1.7 (such as 1.6.x or earlier)
  3. Confirm Author-level or higher users exist
    Go to WordPress admin > Users and review user roles. Author role and above (Editor, Administrator) can exploit this vulnerability
    Affected if At least one user account has Author, Editor, or Administrator role enabled on the site
  4. Inspect plugin URL fetching configuration
    Check the plugin settings page (usually under Settings > Featured Image from Content) for any URL input fields or external URL fetching options, and review the plugin source code for fetch_url or wp_remote_get function calls
    Affected if The plugin contains URL fetching functionality that accepts user-supplied URLs without proper validation
  5. Review access logs for internal resource requests
    Examine server access logs (Apache/nginx error and access logs) for requests to internal IPs (127.0.0.1, 10.x.x.x, 192.168.x.x), localhost, or cloud metadata endpoints (169.254.169.254) originating from the WordPress site
    Affected if Suspicious requests to internal network addresses appear in logs with user agent matching WordPress or the plugin

A user is affected if the featured-image-from-content plugin versions before 1.7 is installed and active, and at least one Author-level or higher user account exists on the WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the featured-image-from-content plugin to version 1.7 or later, which patches the insecure URL fetching functionality. Additionally, restrict Author-level user permissions and monitor for suspicious internal resource requests.

Recommended fix High confidence

version 1.7

  1. Update the Featured Image from Content (featured-image-from-content) WordPress plugin to version 1.7 or later via the WordPress admin dashboard under Plugins > Installed Plugins
  2. Verify the update was successful by confirming the plugin version displays as 1.7 or higher
  3. Confirm that Author-level users can no longer make arbitrary HTTP requests to internal resources through the plugin's URL fetching functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data