{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48093 exists.","fix":"No fix has been published for CVE-2024-48093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48093 is a high-severity vulnerability in n/a, published on 30 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-48093 and fix it if it is affected.\n\nWhat it is: CVE-2024-48093 is a high-severity vulnerability in n/a, published on 30 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48093 exists.\n\nAffected product: n/a. 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-2024-48093/ (Markdown: https://insights.sbomify.com/CVE-2024-48093/index.md)","id":"CVE-2024-48093","markdown":"https://insights.sbomify.com/CVE-2024-48093/index.md","name":"CVE-2024-48093","record":{"aliases":["GHSA-7w36-gg3q-f3vg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Operately web app","requires_auth":"low_privilege","summary":"Privileged users can achieve remote code execution in Operately by uploading malicious files without validation.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted File Upload in the Discussions tab in Operately v.0.1.0 allows a privileged user to achieve Remote Code Execution via uploading and executing malicious files without validating file extensions or content types.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2024-48093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2024-48107"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2024-48091"},"products":["n/a"],"published":"2024-10-30","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-31","vendors":["n/a"]},"summary":"Privileged users can achieve remote code execution in Operately by uploading malicious files without validation.","url":"https://insights.sbomify.com/CVE-2024-48093/"}