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

CVE-2024-33590

MEDIUM · 5.0 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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
Server-Side Request Forgery (SSRF) vulnerability in codeSavory Knowledge Base documentation & wiki plugin – BasePress.This issue affects Knowledge Base documentation & wiki plugin – BasePress: from n/a through 2.16.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 BasePress WordPress plugin. The vulnerability allows an attacker to make the server-side application perform requests to arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationUpdate BasePress plugin to version 2.16.2 or later. If immediate update is not possible, review and restrict outbound network requests from the server and monitor for suspicious internal network access patterns.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 BasePress plugin version
    Check the WordPress admin panel under Plugins > Installed Plugins, or inspect the plugin's main file (usually basepress.php) and look for the 'Version' header comment
    Affected if Cannot locate version or version field is missing
  2. Compare installed version to fixed release
    Compare the installed BasePress version number against 2.16.2 - any version lower than 2.16.2 is affected
    Affected if Installed version is lower than 2.16.2 (e.g., 2.16.1, 2.16.0, 2.15.x, etc.)
  3. Verify plugin is active
    Confirm BasePress is enabled in WordPress admin under Plugins > Installed Plugins - an inactive plugin with a vulnerable version does not expose the SSRF flaw
    Affected if Plugin version is below 2.16.2 AND the plugin is currently activated
  4. Check for SSRF-inducing configuration
    Review BasePress settings in WordPress admin under BasePress > Settings - look for any features that accept URLs, external API endpoints, or allow fetching remote content
    Affected if Vulnerable version is active AND the plugin has URL-fetching or external request features enabled

You are affected if BasePress plugin version is below 2.16.2, the plugin is active, and the vulnerable URL-handling feature is in use or accessible.

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 BasePress plugin to version 2.16.2 or later. If immediate update is not possible, review and restrict outbound network requests from the server and monitor for suspicious internal network access patterns.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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