{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77352 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77352 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77352 is a medium-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 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-77352 and fix it if it is affected.\n\nWhat it is: CVE-2026-77352 is a medium-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77352 in the wild and no public exploit code.\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-77352/ (Markdown: https://insights.sbomify.com/CVE-2026-77352/index.md)","id":"CVE-2026-77352","markdown":"https://insights.sbomify.com/CVE-2026-77352/index.md","name":"CVE-2026-77352","record":{"aliases":["GHSA-c75x-9vj6-57qj"],"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 trigger server-side requests to internal networks via SMTP settings, potentially exposing internal services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. From version 2.0.0 to before version 5.0.0, any authenticated Wallos user (no admin rights required) can make the server open arbitrary outbound SMTP connections to internal/link-local addresses, by setting the SMTP host of their personal email notifications to an internal IP. The per-user notification settings endpoint (endpoints/notifications/saveemailnotifications.php) performs no SSRF validation, and the notification cron (endpoints/cronjobs/sendnotifications.php) feeds that user-controlled host straight into PHPMailer ($mail-\u003eHost = $email['smtpAddress']). When the user's subscription notification fires, the server connects to the chosen host:port. This issue has been patched in version 5.0.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Wallos: Authenticated SSRF via per-user SMTP notification host (low-privilege user)","id":"CVE-2026-77352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Wallos: iCalendar Injection via CRLF in Subscription Name/Notes Export","id":"CVE-2026-77353"},"packages":[],"prev":{"headline":"Wallos: SSRF via Unvalidated User-Level SMTP Host in Email Notification Settings","id":"CVE-2026-77351"},"products":["Wallos"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["ellite"]},"summary":"Authenticated users can trigger server-side requests to internal networks via SMTP settings, potentially exposing internal services.","url":"https://insights.sbomify.com/CVE-2026-77352/"}