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

CVE-2025-5818

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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
The Featured Image Plus – Quick & Bulk Edit with Unsplash plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.6.6 via the fip_get_image_options() function. This makes it possible for authenticated attackers, with administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 Plus plugin for WordPress contains an SSRF vulnerability in the fip_get_image_options() function in all versions up to 1.6.6. Authenticated attackers with administrator-level access can exploit this to make arbitrary web requests from the server, potentially querying internal services or exfiltrating data.

MitigationUpdate the plugin to the latest version once available; if no patch exists, modify the fip_get_image_options() function to validate and sanitize URL inputs, restricting requests to allowed domains or blocking external requests entirely.

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

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. Confirm plugin installation and version
    Locate the Featured Image Plus plugin in the WordPress plugins directory (wp-content/plugins/featured-image-plus or similar) and read the main plugin file header to obtain the installed version number
    Affected if The installed version is 1.6.6 or lower (all versions up to 1.6.6 are affected)
  2. Verify vulnerable function exists
    Search the plugin files for the fip_get_image_options() function definition using grep or a file search within the plugin directory
    Affected if The function exists and accepts URL parameters without proper validation or sanitization
  3. Identify URL parameter handling
    Examine the fip_get_image_options() function code to determine if it processes external URLs provided as input parameters without restricting to allowed domains
    Affected if The function accepts URL input and makes HTTP requests to arbitrary URLs without domain allowlisting or validation
  4. Check for administrator access exposure
    Review WordPress user roles and capabilities to determine if untrusted users have administrator-level privileges, as the vulnerability requires administrator access to exploit
    Affected if Administrator accounts exist and the plugin is accessible to authenticated administrators
  5. Audit server request logs
    Review web server access logs and WordPress debug logs for suspicious outgoing requests originating from the server, particularly to internal IP ranges or unusual external domains initiated by the plugin
    Affected if Outbound requests from the server match patterns typical of SSRF exploitation targeting internal services or unexpected external URLs

You are affected if the Featured Image Plus plugin is installed at version 1.6.6 or lower and the fip_get_image_options() function processes external URLs without validation or domain restrictions.

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 plugin to the latest version once available; if no patch exists, modify the fip_get_image_options() function to validate and sanitize URL inputs, restricting requests to allowed domains or blocking external requests entirely.

Recommended fix Moderate confidence

Version 1.6.7 or later of Featured Image Plus – Quick & Bulk Edit with Unsplash

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Featured Image Plus – Quick & Bulk Edit with Unsplash'
  4. Click 'Update now' if an update is available, or manually upload version 1.6.7 or later from the WordPress plugin repository
  5. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5818 — 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-2025-5818 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