dbcve.org
Instant ImagesWordPress extension · Connekthq

CVE-2023-27451

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 5.1.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Server-Side Request Forgery (SSRF) vulnerability in Darren Cooney Instant Images plugin <= 5.1.0.2 versions.

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 exists in the Instant Images WordPress plugin by Darren Cooney (versions 5.1.0.2 and below). The vulnerability allows attackers to induce the server to make requests to arbitrary URLs, potentially accessing internal services or bypassing network restrictions.

MitigationUpdate the Instant Images plugin to the latest version as soon as a patched release is available. If immediate patching is not possible, consider disabling the plugin or restricting access to the affected functionality via web application firewall rules.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Instant ImagesWordPress extension
Affected:<= 5.1.0.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Instant Images plugin is installed
    Locate the Instant Images plugin directory in the WordPress plugins folder (wp-content/plugins/) or check via WordPress admin plugin list
    Affected if The plugin named 'Instant Images' or 'connekthq/instant-images' appears in the installed plugins list
  2. Identify the installed plugin version
    Open the main plugin file (instant-images.php) or readme.txt and locate the version number in the plugin header comment
    Affected if The version number is 5.1.0.2 or lower (any version up to and including 5.1.0.2)
  3. Verify the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to confirm Instant Images shows as 'Active'
    Affected if The plugin status is Active - an inactive plugin would not be exploitable
  4. Confirm the SSRF-prone feature is accessible
    This plugin provides functionality to fetch images from external URLs (the core purpose of Instant Images is media downloads). Verify this functionality is available to users with the relevant capability.
    Affected if Any user with access to the plugin features (typically admin-level) can trigger outbound HTTP requests through the plugin

A user is affected if the Instant Images plugin versions 5.1.0.2 or below is installed and active on the WordPress site, allowing authenticated users to induce the server to make arbitrary outbound requests.

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
Upgrade available Upgrade to a release after 5.1.0.2
Interim mitigation

Update the Instant Images plugin to the latest version as soon as a patched release is available. If immediate patching is not possible, consider disabling the plugin or restricting access to the affected functionality via web application firewall rules.

Recommended fix Moderate confidence

Latest available version of Instant Images plugin (greater than 5.1.0.2)

  1. Navigate to WordPress dashboard > Plugins > Installed Plugins
  2. Locate the Instant Images plugin
  3. Check the current version installed (vulnerable if <= 5.1.0.2)
  4. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  5. Verify the update was successful and the plugin is now running a version greater than 5.1.0.2

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

Fix this in Instant Images Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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