{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33399 exists.","fix":"No fix has been published for CVE-2026-33399 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33399 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33399 and fix it if it is affected.\n\nWhat it is: CVE-2026-33399 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33399 exists.\n\nAffected product: ellite Wallos. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33399/ (Markdown: https://insights.sbomify.com/CVE-2026-33399/index.md)","id":"CVE-2026-33399","markdown":"https://insights.sbomify.com/CVE-2026-33399/index.md","name":"CVE-2026-33399","record":{"aliases":["GHSA-mfjc-3258-cq3j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wallos subscription tracker","requires_auth":"low_privilege","summary":"Authenticated users can bypass SSRF protections in Wallos by saving internal IPs in notification settings, leading to internal network access via cron jobs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wallos","vendor":"wallosapp"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Wallos: SSRF Bypass - Incomplete Fix for CVE-2026-30839/30840","id":"CVE-2026-33399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Wallos: Stored cross-site scripting (XSS) vulnerability in the payment method rename endpoint","id":"CVE-2026-33400"},"packages":[],"prev":{"headline":"Authenticated users can read hidden forum posts through `/forum/get_quotes`","id":"CVE-2026-33398"},"products":["Wallos"],"published":"2026-03-24","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-55371","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-55372","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":8.8,"headline":"Wallos: Server-Side Request Forgery (SSRF) in Notification Testers","id":"CVE-2026-30840","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":8.7,"headline":"Wallos: SSRF via url parameter leading to File Traversal","id":"CVE-2026-30828","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":8.3,"headline":"Wallos: SSRF via HTTP Proxy Environment Variable","id":"CVE-2026-33407","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2024-29320","kev_date_added":null,"published":"2024-04-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["ellite"]},"summary":"Authenticated users can bypass SSRF protections in Wallos by saving internal IPs in notification settings, leading to internal network access via cron jobs.","url":"https://insights.sbomify.com/CVE-2026-33399/"}