{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77348 exists.","fix":"No fix has been published for CVE-2026-77348 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77348 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77348 and fix it if it is affected.\n\nWhat it is: CVE-2026-77348 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77348 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-77348/ (Markdown: https://insights.sbomify.com/CVE-2026-77348/index.md)","id":"CVE-2026-77348","markdown":"https://insights.sbomify.com/CVE-2026-77348/index.md","name":"CVE-2026-77348","record":{"aliases":[],"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":"none","summary":"Unauthenticated attackers can trigger Server-Side Request Forgery in Wallos via the payments search endpoint due to an incomplete security fix.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 5.0.0, the fix for CVE-2026-33407 (GHSA-hhjq-82f8-m6rc, \"SSRF via HTTP Proxy Environment Variable\") hardened endpoints/logos/search.php by disabling cURL proxying (CURLOPT_PROXY = '' + CURLOPT_NOPROXY = '*'). However, Wallos ships a second, near-identical, unauthenticated logo-image search endpoint — endpoints/payments/search.php — that was not given the same hardening. It still passes the HTTP_PROXY/HTTPS_PROXY environment variable straight into CURLOPT_PROXY. 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":"weaponised"},"has_fix":false,"headline":"Server-side request forgery in Wallos","id":"CVE-2026-77348","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Wallos: SSRF via Unvalidated User-Level SMTP Host in Email Notification Settings","id":"CVE-2026-77351"},"packages":[],"prev":{"headline":"cpp-httplib: CRLF injection via unvalidated HTTP trailer headers in chunked response writing","id":"CVE-2026-77341"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-03","vendors":["ellite"]},"summary":"Unauthenticated attackers can trigger Server-Side Request Forgery in Wallos via the payments search endpoint due to an incomplete security fix.","url":"https://insights.sbomify.com/CVE-2026-77348/"}