Authenticated internal requests via unvalidated notification URLs
Published Mar 24, 2026 · Updated Mar 24, 2026
SSRF in Wallos before 4.7.0 allows remote authenticated users to send server-side requests to internal or private network URLs. The notification save endpoints persist user-supplied webhook URLs after checking only their scheme and syntax, without calling validate_webhook_url_for_ssrf(). When sendnotifications.php later processes a saved URL, the server performs a blind request that can reach internal services or cloud metadata endpoints.
Summary
What happened
SSRF in Wallos before 4.7.0 allows remote authenticated users to send server-side requests to internal or private network URLs. The notification save endpoints persist user-supplied webhook URLs after checking only their scheme and syntax, without calling validate_webhook_url_for_ssrf(). When sendnotifications.php later processes a saved URL, the server performs a blind request that can reach internal services or cloud metadata endpoints.
The record
- CVE
- CVE-2026-33399
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- ellite
- Product
- Wallos
- Classifications
- CWE-918, CAPEC-664
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-mfjc-3258-cq3j proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo