{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55383 exists.","fix":"No fix has been published for CVE-2025-55383 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55383 is a high-severity vulnerability in n/a, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55383 and fix it if it is affected.\n\nWhat it is: CVE-2025-55383 is a high-severity vulnerability in n/a, published on 21 Aug 2025. 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-2025-55383 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-2025-55383/ (Markdown: https://insights.sbomify.com/CVE-2025-55383/index.md)","id":"CVE-2025-55383","markdown":"https://insights.sbomify.com/CVE-2025-55383/index.md","name":"CVE-2025-55383","record":{"aliases":["GHSA-4c9r-p2x5-3f3m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Moss web application","requires_auth":"none","summary":"Attackers can upload arbitrary files to any location on the Moss server, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Moss before v0.15 has a file upload vulnerability. The \"upload\" function configuration allows attackers to upload files of any extension to any location on the target server.","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-2025-55383","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in n/a","id":"CVE-2025-55398"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-55373"},"products":["n/a"],"published":"2025-08-21","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":"2025-08-21","vendors":["n/a"]},"summary":"Attackers can upload arbitrary files to any location on the Moss server, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2025-55383/"}