Wallos incomplete fix for CVE-2026-33407: unauthenticated httpoxy SSRF still reachable via `endpoints/payments/search.php`

published 2026-08-31 2 mo ago modified 2026-09-08 2 mo ago also EUVD-2026-68886

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 5.0.0, the fix for CVE-2026-33407 (GHSA-hhjq-82f8-m6rc, "SSRF via HTTP Proxy Environment Variable") hardened endpoints/logos/search.php by disabling cURL proxying (CURLOPT_PROXY = '' + CURLOPT_NOPROXY = '*'). However, Wallos ships a second, near-identical, unauthenticated logo-image search endpoint — endpoints/payments/search.php — that was not given the same hardening. It still passes the HTTP_PROXY/HTTPS_PROXY environment variable straight into CURLOPT_PROXY. This issue has been patched in version 5.0.0.

Patch / fix

links 2

github.com/ellite/Wallos@11eaf40 commit
github.com/ellite/Wallos/releases/tag/v5.0.0 release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 2 mo ago (2026-09-03)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/ellite/Wallos/security/advisories/GHSA-f8j2-qm83-r2w4 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/ellite/Wallos/security/advisories/GHSA-hhjq-82f8-m6rc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected products

ellite Wallos

Classification

Weakness

CWE-441 Unintended Proxy or Intermediary
CWE-918 Server-Side Request Forgery
CWE-1188 Initialization of a Resource with an Insecure Default

References

Sources

CVE List CVE-2026-77348
NVD CVE-2026-77348

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary