Skip to main content
VulnerabilityPublished Updated

CVE-2026-33407: ellite Wallos · Server-Side Request Forgery (SSRF)

Affects ellite WallosSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High : upgrade to 4.7.0 soon.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.7.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Wallos and ellite/Wallos to 4.7.0.

Affected software

ProductAffectedFixed in
elliteWallosAffected
  • <4.7.0
Fixed in
  • 4.7.0
GitHubellite/Wallospkg:github/ellite/WallosOther threatsAffected
  • <4.7.0
Fixed in
  • 4.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade Wallos to version 4.7.0 or later, where the issue has been patched. Until upgrading is possible, administrators should disable or restrict the use of HTTP_PROXY and HTTPS_PROXY environment variables within the application environment to prevent proxy hijacking. Implement strict input validation and sanitization on all user-supplied data, especially those influencing network requests or environment variables. Network-level controls such as egress filtering and firewall rules should be enforced to restrict outbound traffic from the Wallos server to only trusted destinations. Monitoring and logging outbound requests from the application can help detect anomalous behavior indicative of SSRF exploitation attempts. Additionally, consider deploying web application firewalls (WAFs) with SSRF detection capabilities. Regular security assessments and code reviews focusing on environment variable handling and external request logic are recommended to prevent similar issues.

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.

References

Community reviews

Loading reviews…