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

CVE-2024-43989

HIGH · 7.5 CVSS v3.1 Published 2024-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Firsh Justified Image Grid justified-image-grid.This issue affects Justified Image Grid: from n/a through <= 4.6.1.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the Justified Image Grid WordPress plugin. Attackers can abuse the plugin's functionality to make the server perform arbitrary requests to internal or external resources, potentially accessing sensitive internal services, cloud metadata endpoints, or circumventing network segmentation.

MitigationUpdate the Justified Image Grid plugin to the latest patched version once available. Until then, restrict outgoing network connections from the web server, implement Web Application Firewall rules to block suspicious URL patterns, and audit the plugin's configuration for any user-controllable URL parameters.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/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. Verify Justified Image Grid plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/justified-image-grid/ or view the installed plugins list in the WordPress admin dashboard under Plugins
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugin list
  2. Determine installed plugin version
    Open the main plugin file (justified-image-grid.php) and locate the version comment/constant at the top, or check the readme.txt file in the plugin directory for the 'Stable tag' value
    Affected if The installed version matches the vulnerable version range published by the vendor (compare your version to any affected versions stated in plugin release notes or security advisories)
  3. Identify URL-handling features in plugin settings
    Navigate to the plugin settings in WordPress admin (Justified Image Grid settings page) and look for any fields that accept URLs, remote sources, or feed endpoints - these are potential SSRF attack vectors
    Affected if The plugin has configurable URL parameters, remote source fields, or feed URLs that accept user-supplied or external input
  4. Check for user roles with plugin access
    Review WordPress user roles and capabilities to determine which users can access and configure the Justified Image Grid plugin settings
    Affected if Users other than administrators (such as editors or authors) can modify plugin settings containing URL parameters
  5. Audit network exposure
    Review web server and firewall logs for outgoing requests originating from the web server to internal resources (such as 127.0.0.1, 169.254.169.254 for cloud metadata, or internal IP ranges) that may indicate SSRF exploitation attempts
    Affected if Unexpected outbound connections from the web server to internal IPs, localhost, or cloud metadata endpoints appear in logs

Your environment is affected if the Justified Image Grid plugin is installed and its version falls within the vendor-stated vulnerable range, particularly if URL-handling settings are accessible to users or exposed to visitor traffic.

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 the Justified Image Grid plugin to the latest patched version once available. Until then, restrict outgoing network connections from the web server, implement Web Application Firewall rules to block suspicious URL patterns, and audit the plugin's configuration for any user-controllable URL parameters.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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