Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-30839: CWE-918: Server-Side Request Forgery (SSRF) in ellite Wallos

0
Medium
VulnerabilityCVE-2026-30839cvecve-2026-30839cwe-918
Published: Sat Mar 07 2026 (03/07/2026, 05:29:55 UTC)
Source: CVE Database V5
Vendor/Project: ellite
Product: Wallos

Description

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.6.2, testwebhooknotifications.php does not validate the target URL against private/reserved IP ranges, enabling full-read SSRF. The server response is returned to the caller. This issue has been patched in version 4.6.2.

AI-Powered Analysis

AILast updated: 03/07/2026, 06:01:22 UTC

Technical Analysis

CVE-2026-30839 is a Server-Side Request Forgery (SSRF) vulnerability categorized under CWE-918, affecting ellite's Wallos software versions prior to 4.6.2. Wallos is an open-source, self-hostable personal subscription tracker. The vulnerability exists in the testwebhooknotifications.php script, which fails to validate the target URL against private or reserved IP address ranges. This lack of validation allows an attacker to craft requests that force the server to initiate HTTP requests to arbitrary internal or external resources, including those on private networks. Because the server returns the response from these requests to the attacker, this can lead to unauthorized information disclosure from internal systems that are otherwise inaccessible externally. The vulnerability does not require user interaction but does require the attacker to have low privileges on the server (PR:L). The attack vector is network-based (AV:N), and the attack complexity is low (AC:L). The vulnerability does not require authentication (AT:N), and there is no impact on integrity, availability, or confidentiality beyond the limited information disclosure (VC:L). The issue was patched in Wallos version 4.6.2 by adding proper validation to block requests targeting private or reserved IP ranges. No known exploits are currently reported in the wild, but the vulnerability poses a risk to organizations running outdated versions of Wallos, especially if the vulnerable endpoint is exposed to untrusted networks.

Potential Impact

The primary impact of this SSRF vulnerability is unauthorized information disclosure from internal or protected network resources. Attackers can leverage the vulnerability to access internal services, metadata endpoints, or other sensitive resources that are not directly accessible from the internet. This can lead to reconnaissance that facilitates further attacks such as privilege escalation, lateral movement, or data exfiltration. Since Wallos is a self-hosted subscription tracker, organizations using it may expose internal network infrastructure details or sensitive subscription data. The vulnerability could also be used to bypass firewall rules or access cloud provider metadata services if Wallos is hosted in cloud environments, potentially leading to credential theft or further compromise. Although the CVSS score is medium, the risk increases if the vulnerable endpoint is exposed to the internet or untrusted networks. Organizations with Wallos instances accessible externally or with weak access controls are at higher risk. The lack of known exploits reduces immediate threat but does not eliminate the potential for future exploitation.

Mitigation Recommendations

1. Upgrade Wallos to version 4.6.2 or later immediately to apply the official patch that validates URLs against private and reserved IP ranges. 2. Restrict access to the testwebhooknotifications.php endpoint by implementing network-level controls such as firewalls or VPNs to limit usage to trusted users or systems only. 3. Implement web application firewall (WAF) rules to detect and block SSRF attack patterns targeting Wallos endpoints. 4. Monitor logs for unusual outbound HTTP requests originating from the Wallos server, especially those targeting internal IP ranges or unexpected external domains. 5. Conduct internal network segmentation to limit the impact of SSRF by isolating critical services and metadata endpoints from the Wallos host. 6. Review and harden server permissions to ensure that only authorized users have access to Wallos administrative functions, minimizing the risk of low-privilege exploitation. 7. Educate administrators about the risks of SSRF and encourage regular software updates and security audits for self-hosted applications.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-05T21:06:44.606Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69abbb9ec48b3f10ff5a0866

Added to database: 3/7/2026, 5:46:06 AM

Last enriched: 3/7/2026, 6:01:22 AM

Last updated: 3/8/2026, 2:09:43 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses