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

CVE-2026-57413

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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
Server-Side Request Forgery (SSRF) vulnerability in bdthemes Instant Image Generator ai-image allows Server Side Request Forgery.This issue affects Instant Image Generator: from n/a through <= 2.1.4.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in bdthemes Instant Image Generator ai-image plugin allows attackers to make the server perform arbitrary requests to attacker-controlled destinations, potentially exposing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationUpdate to a version beyond 2.1.4 once the patch is released. Implement input validation with strict allowlists for URL destinations and apply network segmentation to limit outbound requests from the web server.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the plugin version
    Check the installed version of the bdthemes Instant Image Generator ai-image plugin in the WordPress admin dashboard under Plugins, or inspect the plugin's main PHP file header for the 'Version' field
    Affected if The installed version is 2.1.4 or lower
  2. Confirm the plugin is active
    Verify the ai-image plugin is currently activated in the WordPress site plugins list
    Affected if The plugin is active and processing requests
  3. Identify URL-based image input feature
    Locate the plugin settings or image generation interface where users can provide external URLs as input for image generation
    Affected if The feature that accepts external URLs is present and configurable
  4. Check access to the image generation endpoint
    Inspect the plugin's AJAX endpoints or form handlers that process the URL input (typically found in the plugin's main class or ajax-related PHP files)
    Affected if The endpoint accepts and processes arbitrary URLs without strict validation
  5. Verify outbound network access
    Confirm the web server has outbound network access enabled, allowing the plugin to make HTTP requests to arbitrary destinations
    Affected if The server can initiate outbound connections to external URLs provided by users

The environment is affected if the bdthemes Instant Image Generator ai-image plugin is active at version 2.1.4 or lower and the URL-based image generation feature is accessible to users or unauthenticated attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a version beyond 2.1.4 once the patch is released. Implement input validation with strict allowlists for URL destinations and apply network segmentation to limit outbound requests from the web server.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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