{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23943 exists.","fix":"No fix has been published for CVE-2023-23943 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23943 is a medium-severity server-side request forgery vulnerability in nextcloud security-advisories, published on 6 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-23943 and fix it if it is affected.\n\nWhat it is: CVE-2023-23943 is a medium-severity server-side request forgery vulnerability in nextcloud security-advisories, published on 6 Feb 2023. 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-2023-23943 exists.\n\nAffected product: nextcloud security-advisories. 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-2023-23943/ (Markdown: https://insights.sbomify.com/CVE-2023-23943/index.md)","id":"CVE-2023-23943","markdown":"https://insights.sbomify.com/CVE-2023-23943/index.md","name":"CVE-2023-23943","record":{"aliases":["GHSA-8gcx-r739-9pf6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Mail app","requires_auth":"low_privilege","summary":"Attackers can exploit blind SSRF in Nextcloud Mail to scan internal network services via server URL inputs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mail","vendor":"nextcloud"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Nextcloud mail is an email app for the nextcloud home server platform. In affected versions the SMTP, IMAP and Sieve host fields allowed to scan for internal services and servers reachable from within the local network of the Nextcloud Server. It is recommended that the Nextcloud Maill app is upgraded to 1.15.0 or 2.2.2. The only known workaround for this issue is to completely disable the nextcloud mail app.","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":"Blind SSRF via server URL input in the Nextcloud Mail app","id":"CVE-2023-23943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Nexcloud Mail app temporarily stores cleartext password in database","id":"CVE-2023-23944"},"packages":[],"prev":{"headline":"Self reflected HTML injection in Desktop client","id":"CVE-2023-23942"},"products":["security-advisories"],"published":"2023-02-06","related":[{"cvss_score":8.8,"headline":"Missing permission check on email metadata retrieval","id":"CVE-2021-32652","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.3,"headline":"Unauthenticated SSRF in 3rd party module \"cerdic/csstidy\"","id":"CVE-2022-31132","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":8.2,"headline":"Nextcloud Mail auto configurator can be tricked into sending account information to wrong servers","id":"CVE-2024-52508","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":4.3,"headline":"Require strict cookies for image proxy requests in Nextcloud Mail","id":"CVE-2023-45660","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":4.3,"headline":"Bypass of image blocking in Nextcloud Mail","id":"CVE-2021-32707","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":4.1,"headline":"IDOR Vulnerability in Nextcloud Mail","id":"CVE-2023-25160","kev_date_added":null,"published":"2023-02-13"}],"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":"2025-03-10","vendors":["nextcloud"]},"summary":"Attackers can exploit blind SSRF in Nextcloud Mail to scan internal network services via server URL inputs.","url":"https://insights.sbomify.com/CVE-2023-23943/"}