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

CVE-2024-5021

CRITICAL · 9.3 CVSS v3.1 Published 2024-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The WordPress Picture / Portfolio / Media Gallery plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.0.1 via the 'file_get_contents' function. This makes it possible for unauthenticated attackers 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 WordPress Picture/Portfolio/Media Gallery plugin fails to properly validate user-supplied input before passing it to PHP's file_get_contents function, allowing unauthenticated attackers to induce the server to make requests to arbitrary URLs. This SSRF vulnerability enables attackers to probe internal services, bypass firewalls, and potentially exfiltrate sensitive data from internal network resources.

MitigationUpdate the plugin to version 3.0.2 or later which contains the patch. If no update is available, disable and remove the plugin until a patched version is released.

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

CVSS:3.1/AV:N/AC:L/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. Identify if the plugin is installed
    Check the WordPress plugins directory for 'media-gallery' or 'picture-portfolio' plugin folders, or use WP-CLI: wp plugin list --name='media-gallery'
    Affected if The plugin is present in the plugins directory or listed by WP-CLI
  2. Determine the installed plugin version
    Read the main plugin PHP file (usually media-gallery.php or similar) and locate the 'Version' header in the plugin comments, or use: wp plugin get media-gallery --format=json
    Affected if Version is present and lower than 3.0.2 (the patched version)
  3. Verify the plugin is active
    Check WordPress admin panel under Plugins > Installed Plugins, or use: wp plugin status media-gallery
    Affected if Plugin status shows as 'Active' and version is below 3.0.2
  4. Inspect server access logs for suspicious requests
    Review web server access logs (Apache/nginx) for requests to the plugin endpoints containing unusual URLs (internal IP ranges like 127.0.0.1, 192.168.x.x, 10.x.x.x, or unusual query parameters)
    Affected if Logs show requests from the server itself to internal endpoints or known SSRF probe patterns
  5. Check for recent unauthorized modifications
    Compare plugin files against known good backups or check file integrity using: find /path/to/wp-content/plugins/media-gallery -type f -mtime -7
    Affected if Unexpected recent file modifications in the plugin directory

The environment is affected if the WordPress Picture/Portfolio/Media Gallery plugin is installed, active, and running on a version lower than 3.0.2.

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 version 3.0.2 or later which contains the patch. If no update is available, disable and remove the plugin until a patched version is released.

Recommended fix Moderate confidence

Picture / Portfolio / Media Gallery plugin version 3.0.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Picture / Portfolio / Media Gallery' plugin
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and update all available plugins
  7. After updating, verify the plugin is running version 3.0.2 or later

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

Have this fixed 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 help mitigating

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-2024-5021 — 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-5021 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