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

CVE-2025-47437

MEDIUM · 6.4 CVSS v3.1 Published 2025-09-09
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

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 LiteSpeed Technologies LiteSpeed Cache litespeed-cache.This issue affects LiteSpeed Cache: from n/a through <= 7.0.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

Server-Side Request Forgery (SSRF) vulnerability in LiteSpeed Cache allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This could enable access to internal services, cloud metadata endpoints, or network reconnaissance.

MitigationUpdate LiteSpeed Cache to the latest patched version immediately. If no patch is available, disable URL-fetching features in the plugin and restrict outbound network access 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. Identify if LiteSpeed Cache is installed
    Check your WordPress installation for the LiteSpeed Cache plugin. In WordPress admin, go to Plugins > Installed Plugins and look for 'LiteSpeed Cache'. Alternatively, check for the presence of /wp-content/plugins/litespeed-cache/ directory.
    Affected if LiteSpeed Cache plugin is present on the WordPress site
  2. Determine installed LiteSpeed Cache version
    In WordPress admin, go to Plugins > Installed Plugins > LiteSpeed Cache and view the version number. Alternatively, check the plugin's main PHP file header or version.php for the version constant.
    Affected if The installed version falls within any affected version range (compare your version against official LiteSpeed security advisories)
  3. Check if URL-fetching feature is enabled
    In WordPress admin, navigate to LiteSpeed Cache > Cache > URL Fetch settings, or look for any configuration allowing the plugin to make outbound HTTP requests. Check if this feature is turned ON or enabled.
    Affected if The URL-fetching or similar outbound request feature is enabled in LiteSpeed Cache settings
  4. Verify network exposure
    Review your web server firewall or network ACLs to determine if outbound HTTP/HTTPS connections from the web server are unrestricted. Check if internal endpoints (like 127.0.0.1, 169.254.169.254 for cloud metadata) are accessible from the server.
    Affected if The web server can make outbound HTTP requests to arbitrary destinations without restriction

You are affected if LiteSpeed Cache is installed with URL-fetching features enabled, allowing an attacker to induce your server to make arbitrary HTTP requests to internal or external resources.

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 LiteSpeed Cache to the latest patched version immediately. If no patch is available, disable URL-fetching features in the plugin and restrict outbound network access from the web server.

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-2025-47437 — 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-2025-47437 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