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

CVE-2025-60161

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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 bdthemes ZoloBlocks zoloblocks allows Server Side Request Forgery.This issue affects ZoloBlocks: from n/a through <= 2.3.11.

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

Server-Side Request Forgery (SSRF) vulnerability in the ZoloBlocks WordPress plugin allows unauthenticated attackers to make the server perform arbitrary HTTP requests to internal or external resources, potentially exposing internal services, cloud metadata endpoints, or bypassing network segmentation.

MitigationUpdate ZoloBlocks to the latest version which should contain proper input validation and URL allow-listing to prevent SSRF attacks. If no update is available, restrict outgoing network connections from the web server and disable the vulnerable functionality until a patch 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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. Verify ZoloBlocks plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'ZoloBlocks' in the list of active plugins. Alternatively, check the /wp-content/plugins/ directory for a folder named 'zoloblocks'.
    Affected if ZoloBlocks plugin is present and active on the WordPress site
  2. Identify installed ZoloBlocks version
    In WordPress admin, click on the ZoloBlocks plugin entry to view its details, which typically displays the version number. Alternatively, open the main plugin file (e.g., /wp-content/plugins/zoloblocks/zoloblocks.php) and look for the 'Version' header in the plugin metadata comment block.
    Affected if The installed version is older than the patched version containing proper URL validation (compare your version to the latest available release)
  3. Locate URL-fetching functionality
    Search plugin files for functions that perform HTTP requests (look for wp_remote_get, wp_remote_post, file_get_contents with URLs, or cURL calls). Check plugin settings pages in WordPress admin for features that accept URL inputs such as content embedding, data fetching, or external resource loading.
    Affected if The plugin contains features that accept user-supplied URLs and make server-side HTTP requests without proper validation
  4. Confirm the vulnerable endpoint is accessible
    Check if any publicly accessible plugin endpoints or AJAX actions accept URL parameters. Review plugin PHP files for add_action calls with 'wp_ajax' or 'wp_ajax_nopriv' hooks that process URL parameters. Test if unauthenticated requests can reach these handlers.
    Affected if URL-fetching functionality is exposed to unauthenticated users (no login required to exploit)
  5. Review network egress controls
    Inspect server firewall rules, WordPress security plugins, or network configuration to determine if the web server is permitted to make arbitrary outbound HTTP/HTTPS connections. Check if internal network ranges (e.g., 10.x.x.x, 192.168.x.x, 169.254.x.x for metadata) are reachable from the server.
    Affected if The server has unrestricted outbound network access, enabling potential SSRF payloads to reach internal services or cloud metadata endpoints

Your environment is affected if ZoloBlocks is installed with a version lacking proper URL validation, and the vulnerable URL-fetching feature is accessible to attackers without authentication.

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 ZoloBlocks to the latest version which should contain proper input validation and URL allow-listing to prevent SSRF attacks. If no update is available, restrict outgoing network connections from the web server and disable the vulnerable functionality until a patch is released.

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