CVE-2026-92222 is a Server-Side Request Forgery (SSRF) vulnerability affecting Joomla! CMS versions 4.0.0 through 5.4.8 and 6.0.0 through 6.1.3. The issue arises from improper validation of URLs used in server-side requests within various core extensions. This flaw could allow an attacker with high privileges to induce the server to make unauthorized requests. The vulnerability has a high severity rating with a CVSS 4.0 score of 8.9.
CVE-2026-102722 is a server-side request forgery (SSRF) vulnerability in the FTP client of Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a. The client in IPv4 passive mode connects to the address specified by the FTP server's 227 reply rather than the server it is communicating with. This allows a malicious FTP server to cause the client to connect to arbitrary hosts and ports accessible to the device, potentially scanning internal networks or delivering unauthorized uploads to internal services.
PyJWT versions prior to 2.14.0 contain a vulnerability in the PyJWKClient component where HTTP redirects during JWKS fetching are followed without validating the redirect destination. This can lead to exposure of sensitive request headers and allow an attacker-influenced redirect to poison JWKS trust, potentially causing acceptance of forged JWTs. The issue requires an attacker to influence the configured JWKS endpoint's response and is not triggered by token key IDs alone. The vulnerability is fixed in PyJWT 2.14.0.
The ip-address JavaScript library prior to version 10.5.1 contains an incorrect comparison vulnerability in its IPv6 link-local address detection. The Address6 isLinkLocal method only recognizes the fe80::/64 range instead of the full fe80::/10 range, causing inconsistent classification of certain link-local addresses. This inconsistency can allow an attacker-controlled address within the broader fe80::/10 range to bypass trust-boundary checks relying on isLinkLocal, potentially reaching on-link hosts outside intended boundaries. The issue is fixed in version 10.5.1.
A Server-Side Request Forgery (SSRF) vulnerability exists in the ip-address JavaScript library versions 10.2.0 through 10.5.0. The issue arises because the Address6 isPrivate classifier does not recognize the NAT64 local-use range 64:ff9b:1::/48, potentially allowing internal IPv4 destinations encoded through this range to be treated as external. This can lead to bypassing network trust boundaries in applications that rely on isPrivate, isLoopback, and isLinkLocal for trust decisions. The vulnerability is fixed in version 10.5.1.
CVE-2026-55160 is a Server-Side Request Forgery (SSRF) vulnerability in the stringer-rss Stringer application, a self-hosted RSS reader. Before a specific patch commit, authenticated users could make the server send arbitrary HTTP/HTTPS requests to internal networks, localhost, and cloud metadata endpoints such as AWS IMDS. This vulnerability allows low-privileged users, especially when self-service signup is enabled, to scan internal services or potentially steal cloud IAM credentials. The issue has been patched in commit 75cb095.
fast-mcp-telegram versions prior to 30.1 contain a server-side request forgery (SSRF) vulnerability in the send_message and send_message_to_phone MCP tools. These tools accept files as lists of HTTP(S) URLs, which the server downloads and attaches to outgoing Telegram messages. The URL validation relies on a denylist that checks only the hostname string without DNS resolution, allowing attackers to bypass restrictions and cause the server to fetch resources from internal or private network addresses. This results in a full-read SSRF that can exfiltrate data by returning the fetched content as a Telegram file attachment. The vulnerability is patched in version 30.1.
Server-Side Request Forgery (SSRF) in Apache Roller 6.1.5 allows an authenticated user with entry-editing rights on a weblog to cause outbound HTTP requests to attacker-chosen destinations through legacy outbound Trackback and entry enclosure handling. The Trackback control is hidden in the standard UI, but its action remains directly reachable; the enclosure path is relevant only when an author supplies an enclosure URL. No non-default server configuration is required, and the default empty Trackback allow-list permits all destinations. Requests can reach loopback and private-network addresses, while enclosure handling exposes response status, content type, and length. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which removes the outbound trackback action and stops dereferencing enclosure URLs.
A Server-Side Request Forgery (SSRF) vulnerability exists in the Modules Anywhere (Pro) extension for Joomla versions 1.5.0 through 9.0.5. The vulnerability arises because the extension allows additional attributes on a module tag to replace arbitrary parameters of the selected module without verifying the content author. This can lead to SSRF when the replaced parameter is consumed by modules such as Joomla's core Feed module, which accepts local file and network URLs.
CVE-2026-89003 is a Server-Side Request Forgery (SSRF) vulnerability in the WPeMatico RSS Feed Fetcher WordPress plugin versions before 2.8.27. It allows users with contributor-level access or higher to make the server send requests to internal-only hosts and read the responses without proper capability checks.
CVE-2026-89000 is a server-side request forgery (SSRF) vulnerability in the WPeMatico RSS Feed Fetcher WordPress plugin versions before 2.8.27. The plugin does not validate or restrict the destination of user-supplied feed URLs and lacks capability checks, allowing users with contributor-level access or higher to make the server fetch internal-only resources and read the responses.
The Testimonials Widget WordPress plugin up to version 4.0.4 contains a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated users to supply a URL that the server fetches without proper validation, potentially enabling internal service requests and exposure of their responses. The vulnerability has a medium severity rating with a CVSS score of 5.8.
The Asset CleanUp: Page Speed Booster plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.4.0.5 via the 'page_url' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. This vulnerability is only reachable when the plugin's dom_get_type setting has been configured to 'wp_remote_post' by an administrator.
The Link Library WordPress plugin before 7.9.6 does not validate the destination of a user-supplied URL before falling back to an unprotected fetch when its safe request is rejected, allowing unauthenticated visitors to make the site issue requests to hosts on its internal network and to learn from the response whether an internal service answered.
Versions below 7.8.8 are covered by CVE-2025-68600; this entry covers 7.8.8 through 7.9.5, where that fix was incomplete. Exploitation requires the site owner to have published the Link Library WordPress plugin before 7.9.6's public link submission form with reciprocal-link validation enabled.
The client-side field level encryption support in the MongoDB Python Driver can treat a key management endpoint value ending in ".sock" as a local Unix domain socket path rather than a remote host. A user with write access to the encryption key metadata stored in the database can cause an application using the driver to open connections to local sockets on the application host. Data sent over these connections is limited to the start of a TLS handshake, so no chosen content is transmitted.
TREK is a collaborative travel planner. Prior to 3.4.0, the checkSsrf logic in server/src/utils/ssrfGuard.ts does not recognize NAT64, 6to4, or Teredo IPv6 transition addresses that encode an IPv4 destination. An authenticated user who controls a DNS record can supply a URL whose AAAA result is a transition address embedding a private, loopback, or link-local IPv4 target, and isAlwaysBlocked and isPrivateNetwork classify the address as allowed. In a deployment that routes the applicable transition format, user-facing imports, webhooks, integrations, or plugin egress can reach internal services or cloud metadata and expose returned information. This issue is fixed in version 3.4.0.
TREK is a collaborative travel planner. Prior to 3.3.0, TREK allows an authenticated user to store an attacker-controlled llm_base_url through the settings API when the LLM_PARSING feature is enabled. Write permission to the target trip instance is required to trigger the vulnerable AI-assisted import path. The value is consumed by the clients in server/src/nest/llm-parse/clients/openai-compatible.client.ts, server/src/nest/llm-parse/clients/anthropic.client.ts, and server/src/nest/llm-parse/router/ollama-format.client.ts without applying the server-side request forgery guard. Triggering AI-assisted trip parsing causes the server to request the supplied destination, and upstream error response text can be returned in parsing warnings. This permits internal service discovery and access to link-local cloud metadata, with possible disclosure of infrastructure credentials and subsequent modification of protected cloud resources. This issue is fixed in version 3.3.0.
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.5.0 until 2.5.1, the /homepage/proxy endpoint accepts an authenticated user's url query parameter and passes it to http.get or https.get without destination restrictions. In src/backend/database/routes/homepage-proxy-routes.ts, new URL performs only syntactic validation, allowing requests to loopback, RFC1918, link-local, and cloud metadata destinations. The endpoint returns the complete fetched JSON response, so a low-privilege or self-registered account can exfiltrate internal service data and cloud credentials. This issue is fixed in version 2.5.1.
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.5.0 until 2.5.1, Termix allows authenticated users to configure webhook or ntfy notification channels with attacker-controlled destination URLs and trigger server-side requests through the notification-channel test endpoint. The request path in src/backend/database/routes/alert-rules-routes.ts reaches src/backend/utils/notification-sender.ts without destination allowlisting or private-address blocking. This permits blind requests to internal HTTP services reachable by the Termix server. Webhook mode also permits attacker-controlled HTTP methods and headers, which can cause limited state changes when an internal service accepts the fixed notification body, although response bodies are not returned. This issue is fixed in version 2.5.1.
BentoPDF is a client-side PDF toolkit that is self hostable. In 2.8.6 and earlier, the certificate and timestamp CORS proxy in cloudflare/cors-proxy-worker.js uses isPrivateOrReservedHost() to validate a supplied hostname separately from the DNS resolution used by fetch(targetUrl), allowing an attacker-controlled hostname to resolve to an internal or reserved destination after validation. A certificate-like path can satisfy ALLOWED_PATH_PATTERNS, and direct clients can forge the browser-oriented Origin header. Deployments without PROXY_SECRET skip the optional signature check, while the signature is an anti-abuse measure rather than a destination-security boundary. The proxy has a 10 MB response limit and can relay response bodies from reachable destinations. The advisory identifies both the official Worker deployment and self-hosted instances as impacted where the Worker execution environment can reach internal or reserved destinations. This vulnerability is fixed in 2.8.7.