CVE-2026-33407
Received Received - Intake

SSRF via Proxy Hijacking in Wallos search.php Before

Vulnerability report for CVE-2026-33407, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-03-24

Last updated on: 2026-03-26

Assigner: GitHub, Inc.

Description

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, Wallos endpoints/logos/search.php accepts HTTP_PROXY and HTTPS_PROXY environment variables without validation, enabling SSRF via proxy hijacking. The server performs DNS resolution on user-supplied search terms, which can be controlled by attackers to trigger outbound requests to arbitrary domains. This issue has been patched in version 4.7.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-03-24
Last Modified
2026-03-26
Generated
2026-07-06
AI Q&A
2026-03-24
EPSS Evaluated
2026-07-04
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wallosapp wallos to 4.7.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-922 The product stores sensitive information without properly limiting read or write access by unauthorized actors.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-33407 is a critical Server-Side Request Forgery (SSRF) vulnerability in the Wallos package versions up to 4.6.2, specifically in the endpoint endpoints/logos/search.php.

The vulnerability occurs because this endpoint accepts the HTTP_PROXY and HTTPS_PROXY environment variables without validation and directly uses them to configure proxy settings in cURL requests.

Attackers can exploit this by controlling DNS resolution targets through user-supplied search terms, which the server processes without proper validation, enabling them to hijack proxy configurations and trigger outbound requests to arbitrary domains.

  • Access internal network services if the proxy routes internally.
  • Perform DNS-based out-of-band attacks for data exfiltration.
  • Enumerate cloud metadata services (e.g., 169.254.169.254).
  • Conduct SSRF chain attacks in cloud environments.
  • Perform DNS rebinding attacks.
Impact Analysis

This vulnerability can have serious impacts including unauthorized access and reconnaissance of internal network services, which are normally protected from external access.

Attackers can exfiltrate sensitive data using DNS-based out-of-band techniques.

It allows enumeration of cloud metadata services, potentially exposing sensitive cloud instance information.

The vulnerability can be used to chain SSRF attacks in cloud environments, increasing the attack surface and potential damage.

Overall, it can lead to significant security breaches including data leakage and unauthorized internal network access.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring outbound DNS queries triggered by the vulnerable endpoint when processing user-supplied search terms. A proof of concept involves setting up a DNSLog listener to observe DNS resolution requests initiated by the server.'}, {'type': 'paragraph', 'content': 'Specifically, sending crafted search queries to the vulnerable endpoint `endpoints/logos/search.php` with controlled DNS names can trigger outbound DNS requests observable on a DNSLog platform.'}, {'type': 'paragraph', 'content': 'Commands to detect this might include using tools like curl or wget to send requests to the vulnerable endpoint with payloads that cause DNS lookups, and monitoring DNS logs or using DNSLog services to capture these outbound DNS queries.'}, {'type': 'list_item', 'content': 'Set up a DNSLog listener or use a DNS monitoring tool to capture outbound DNS requests.'}, {'type': 'list_item', 'content': "Send HTTP GET requests to the vulnerable endpoint with search terms designed to trigger DNS resolution, e.g., using curl: `curl 'http://<wallos-server>/endpoints/logos/search.php?search=attacker-controlled-domain.com'`."}, {'type': 'list_item', 'content': 'Check DNS logs or DNSLog platform for any outbound DNS queries to attacker-controlled domains.'}] [1]

Mitigation Strategies

[{'type': 'paragraph', 'content': 'Immediate mitigation steps include disabling or validating the `HTTP_PROXY` and `HTTPS_PROXY` environment variables before they are used by the vulnerable endpoint.'}, {'type': 'paragraph', 'content': 'Explicitly disable proxy usage in the code by setting cURL options to prevent proxy hijacking.'}, {'type': 'list_item', 'content': "Disable proxy usage by adding `curl_setopt($ch, CURLOPT_PROXY, '')` and `curl_setopt($ch, CURLOPT_NOPROXY, '*')` in the code handling the requests."}, {'type': 'list_item', 'content': 'Validate or sanitize the `HTTP_PROXY` and `HTTPS_PROXY` environment variables to ensure they cannot be manipulated by attackers.'}, {'type': 'list_item', 'content': 'Employ a centralized SSRF validation helper (e.g., `ssrf_helper.php`) to consistently validate URLs and prevent SSRF attacks.'}, {'type': 'paragraph', 'content': 'Ultimately, upgrade Wallos to version 4.7.0 or later, where this vulnerability has been patched.'}] [1]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-33407. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart