Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 5.0.0, Wallos lets any authenticated user store an arbitrary SMTP host — including private and cloud-metadata IP addresses — in their personal email notification settings, with no server-side SSRF validation. When the scheduled notification cron job runs, it passes the stored host directly to PHPMailer, causing the Wallos server to open an outbound TCP connection to whatever address the attacker specified. This gives a low-privileged attacker a reliable mechanism to probe internal network services from the server's perspective. This issue has been patched in version 5.0.0.
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, Admin-configured OIDC token_url and user_info_url in includes/oidc/handle_oidc_callback.php:18-49 are used directly in curl_init() with zero SSRF filtering. Unlike logo/webhook URLs which have validate_webhook_url_for_ssrf(), OIDC URLs bypass all protections. Admin sets URL to http://169.254.169.254/latest/meta-data/ for cloud metadata access or internal network pivoting. This issue has been patched in version 4.9.6.
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, POST /endpoints/notifications/testemailnotifications.php accepts smtpaddress and smtpport from POST body with zero SSRF validation. PHPMailer connects to attacker-supplied host:port. Every other notification endpoint uses ssrf_helper.php but email was missed. Any authenticated user can probe internal network, cloud metadata. This issue has been patched in version 4.9.6.
elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. Prior to 2.1.70, elFinder URL uploads in php/elFinder.class.php can bypass server-side request forgery protections when PHP cURL is unavailable because validate_address() validates $info['ip'], but get_remote_contents() selects fsock_get_contents(), which connects to $arr['host'] and performs a second DNS resolution. An attacker able to submit a URL upload can use DNS rebinding to have the first resolution return a public address and the connection resolution return a loopback or private address, causing the internal HTTP response body to be stored as an uploaded file and made readable through elFinder. After a successful fetch, get_headers($url, true) separately requests the original hostname without reusing the validated and pinned connection, creating an additional blind server-side request forgery path even when curl_get_contents() is selected. This issue is fixed in version 2.1.70.
oasdiff-action is a GitHub Action that detects breaking changes in OpenAPI specs and post a review on every pull request. Before version 0.0.51, the oasdiff actions resolved external $refs in the OpenAPI spec by default (allow-external-refs: true). When an action runs on a pull request whose spec is attacker-controlled — most importantly fork pull requests on public repositories — a $ref in that spec is fetched/read on the runner with no interaction required, enabling SSRF and disclosure of structured files on the runner. This issue has been patched in version 0.0.51.
CVE-2026-79747 is a Server-Side Request Forgery (SSRF) vulnerability in samanhappy's MCPHub prior to version 1.0.32. An authenticated non-admin user can register a server with an arbitrary URL, causing the hub to issue server-side requests without egress filtering, including to loopback and private IP ranges. The vulnerability allows full response reflection via the OpenAPI proxy path and blind requests via the SSE/streamable-http transport. This issue has been patched in version 1.0.32.
CVE-2026-79749 is a Server-Side Request Forgery (SSRF) vulnerability in samanhappy mcphub prior to version 1.0.32. The vulnerability arises because the SSRF guard does not check certain IPv6 transition address families, allowing attackers to bypass protections by encoding private IPv4 addresses within these IPv6 formats. This can enable unauthorized access to internal infrastructure. The issue has been patched in version 1.0.32.
CVE-2026-58301 is a server-side request forgery (SSRF) vulnerability in Apache Shiro when used with the Jakarta EE integration module. It allows a low-privileged user to craft HTTP requests that cause the server to connect to attacker-controlled URLs and send attacker-controlled data. This affects Apache Shiro versions from 2.0.0-alpha-0 up to and including 3.0.0. The issue is fixed in version 3.0.1 and later. Alternatively, system properties can be set to restrict allowed hosts and ports for form resubmission connections.
In MITRE SAF Heimdall 2.11.6 through 2.13.x before 2.14.0, an SSRF issue allows remote attackers to access internal network resources via the Tenable proxy endpoint. This occurs in apps/backend/src/tenable/tenable.controller.ts.
The 爱采集数据采集和发布插件 WordPress plugin up to version 1.0.0 contains a critical server-side request forgery (SSRF) vulnerability. This flaw arises because the plugin uses a hardcoded default secret for an unauthenticated endpoint and fails to validate URLs or destination paths. Exploitation allows unauthenticated attackers to read arbitrary files on the server, make arbitrary HTTP requests, and write attacker-controlled content outside the uploads directory.
CVE-2026-16947 is a critical Server-Side Request Forgery (SSRF) vulnerability in the Total processing card payments for WooCommerce WordPress plugin up to version 7.3. The plugin fails to validate user-supplied paths before using them to build server-side verification requests and does not verify the authenticity of responses. This allows unauthenticated attackers to redirect verification requests to arbitrary hosts, potentially disclosing merchant payment-gateway credentials and forging success responses that mark arbitrary WooCommerce orders as paid.
SmartAIPress WordPress plugin versions through 1.2.0 contain a Server-Side Request Forgery (SSRF) vulnerability. This occurs because the plugin does not perform capability checks on a specific AJAX action and fails to validate user-supplied URLs before fetching them server-side. As a result, users with subscriber-level access or higher can make the site retrieve arbitrary internal or external URLs and read the responses.
IBM Langflow OSS versions 1.0.0 through 1.11.1 contain a server-side request forgery (SSRF) vulnerability. An authenticated attacker could exploit this flaw to send unauthorized requests from the affected system. This may enable network enumeration or assist in other attacks. The vulnerability has a medium severity rating with a CVSS score of 4.3. No official patch or remediation guidance has been provided by the vendor at this time.
CVE-2026-55245 is a Server-Side Request Forgery (SSRF) vulnerability in maximhq bifrost, an enterprise AI gateway. The issue arises from incorrect classification of certain IP address ranges as public in the isPublicIP function prior to version 1.5.17. This misclassification allows a remote attacker controlling a multimodal request URL to make the gateway fetch internal services, including cloud instance metadata endpoints encoded via IPv6 6to4 or NAT64. The vulnerability has a high severity with a CVSS score of 8.7 and is fixed in version 1.5.17.
Kubeflow Pipelines versions prior to 2.17.0 contain an unauthenticated server-side request forgery (SSRF) vulnerability in the frontend proxy middleware. This flaw allows attackers to send arbitrary HTTP or HTTPS requests to internal services without authentication, bypassing authorization controls. The vulnerability arises because the proxy route does not filter or restrict target addresses and remains accessible even when authorization is enabled. Exploitation can lead to unauthorized access to sensitive internal endpoints, including cloud metadata services and Kubernetes APIs. The issue is fixed in version 2.17.0.
The Everest Forms WordPress plugin is vulnerable to a Server-Side Request Forgery (SSRF) issue in all versions up to and including 3.4.4. The vulnerability arises from the plugin's handling of upload fields, where arbitrary URLs from POST data are passed to a WordPress HTTP function without domain restrictions. This allows unauthenticated attackers to make the server perform outbound HTTP HEAD requests to arbitrary URLs by submitting a specially crafted form.
CVE-2026-78498 is a server-side request forgery (SSRF) vulnerability in WatchGuard Dimension's Email Server Test configuration. It allows an authenticated privileged attacker to enumerate exposed network services on adjacent network systems. The vulnerability affects version 2.0 of WatchGuard Dimension. The CVSS 4.0 score is 5.1, indicating a medium severity level. No official patch or remediation guidance has been provided by the vendor at this time.
CVE-2026-78495 is a server-side request forgery (SSRF) vulnerability in WatchGuard Dimension's Remote Backup Connection Test configuration. It allows an authenticated privileged attacker to enumerate network services on adjacent systems. The vulnerability affects version 2.0 of WatchGuard Dimension. The CVSS 4.0 base score is 5.3, indicating medium severity.
CVE-2026-78499 is a server-side request forgery (SSRF) vulnerability in WatchGuard Dimension's FTP Server Test configuration. It allows an authenticated user with privileged access to enumerate network services on adjacent systems. The vulnerability has a medium severity score of 5.1 and affects version 2.0 of WatchGuard Dimension. No official patch or remediation guidance is currently available from the vendor.