{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46730 exists.","fix":"No fix has been published for CVE-2023-46730 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46730 is a high-severity server-side request forgery vulnerability in Intermesh groupoffice, published on 7 Nov 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-46730 and fix it if it is affected.\n\nWhat it is: CVE-2023-46730 is a high-severity server-side request forgery vulnerability in Intermesh groupoffice, published on 7 Nov 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-46730 exists.\n\nAffected product: Intermesh groupoffice. 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-46730/ (Markdown: https://insights.sbomify.com/CVE-2023-46730/index.md)","id":"CVE-2023-46730","markdown":"https://insights.sbomify.com/CVE-2023-46730/index.md","name":"CVE-2023-46730","record":{"aliases":["GHSA-vw6c-h82w-mvfv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Group-Office CRM","requires_auth":"low_privilege","summary":"Attackers can exploit SSRF in Group-Office to access internal resources and server files via unfiltered URL parameters in the upload API.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"group_office","vendor":"group-office"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Group-Office is an enterprise CRM and groupware tool. In affected versions there is full Server-Side Request Forgery (SSRF) vulnerability in the /api/upload.php endpoint. The /api/upload.php endpoint does not filter URLs which allows a malicious user to cause the server to make resource requests to untrusted domains. Note that protocols like file:// can also be used to access the server disk. The request result (on success) can then be retrieved using /api/download.php. This issue has been addressed in versions 6.8.15, 6.7.54, and 6.6.177. Users are advised to upgrade. There are no known workarounds for this vulnerability.","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 groupoffice","id":"CVE-2023-46730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Remote code execution through the section parameter in Administration as guest in XWiki Platform","id":"CVE-2023-46731"},"packages":[],"prev":{"headline":"Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint","id":"CVE-2023-46729"},"products":["groupoffice"],"published":"2023-11-07","related":[{"cvss_score":9.4,"headline":"Group-Office is vulnerable to RCE due to Command Injection via TNEF Attachment Handler","id":"CVE-2026-25512","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":9.4,"headline":"Group-Office Argument Injection in MaintenanceController::actionZipLanguage","id":"CVE-2026-25134","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2025-63406","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":8.2,"headline":"Group-Office is vulnerable to SSRF and File Read in WOPI service discovery","id":"CVE-2026-25511","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":6.9,"headline":"Group-Office has a Stored XSS Vulnerability via user's name field","id":"CVE-2025-25191","kev_date_added":null,"published":"2025-03-06"},{"cvss_score":6.5,"headline":"Stored Cross-site Scripting Vulnerability via Malicious File Names in GroupOffice","id":"CVE-2024-22418","kev_date_added":null,"published":"2024-01-18"}],"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":"total"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["Intermesh"]},"summary":"Attackers can exploit SSRF in Group-Office to access internal resources and server files via unfiltered URL parameters in the upload API.","url":"https://insights.sbomify.com/CVE-2023-46730/"}