Skip to main content
CVE-2026-33399VulnerabilityPublished

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

Affects ellite WallosSource CVE Database V5

0

Mentioned vulnerabilities

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A: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 2026-10-25.

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 SSRF fix is fully implemented. Until upgrading is possible, administrators should audit and restrict notification URLs configured by users, ensuring no internal or private IP addresses are allowed. Implement network-level controls such as firewall rules or egress filtering to prevent the Wallos server from making HTTP requests to internal IP ranges. Additionally, enforce strict authentication and authorization policies to limit access to Wallos to trusted users only. Monitoring and logging of outgoing requests from the Wallos server can help detect suspicious SSRF exploitation attempts. Finally, consider isolating the Wallos server in a segmented network zone with limited access to critical internal resources to reduce potential impact.

Description

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, the SSRF fix applied in version 4.6.2 for CVE-2026-30839 and CVE-2026-30840 is incomplete. The validate_webhook_url_for_ssrf() protection was added to the test* notification endpoints but not to the corresponding save* endpoints. An authenticated user can save an internal/private IP address as a notification URL, and when the cron job sendnotifications.php executes, the request is sent to the internal IP without any SSRF validation. This issue has been patched in version 4.7.0.

References

Community reviews

Loading reviews…