{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-3518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3518 is a medium-severity vulnerability in Unblu Spark, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-3518 and fix it if it is affected.\n\nWhat it is: CVE-2025-3518 is a medium-severity vulnerability in Unblu Spark, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-3518 in the wild and no public exploit code.\n\nAffected product: Unblu Spark. 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-3518/ (Markdown: https://insights.sbomify.com/CVE-2025-3518/index.md)","id":"CVE-2025-3518","markdown":"https://insights.sbomify.com/CVE-2025-3518/index.md","name":"CVE-2025-3518","record":{"aliases":["GHSA-4mxw-7rp7-fhjr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Unblu Spark","requires_auth":"low_privilege","summary":"Attackers can upload files via direct API requests even when file upload functionality is disabled in the configuration.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"spark","vendor":"unblu"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"It technically possible for a user to upload a file to a conversation despite the file upload functionality being disabled.\n\nThe file upload functionality can be enabled or disabled for specific use cases through configuration. In case the functionality is disabled for at least one use case, the system nevertheless allows files to be uploaded through direct API requests. During the upload file, interception and allowed file type rules are still applied correctly.\n\nIf file sharing is generally enabled, this issue is not of concern.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"File upload functionality possible even when disabled","id":"CVE-2025-3518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Replace uploaded files knowing the file upload ID","id":"CVE-2025-3519"},"packages":[],"prev":{"headline":"Privilege escalation in Devolutions Server","id":"CVE-2025-3517"},"products":["Unblu Spark"],"published":"2025-04-22","related":[],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-24","vendors":["Unblu inc."]},"summary":"Attackers can upload files via direct API requests even when file upload functionality is disabled in the configuration.","url":"https://insights.sbomify.com/CVE-2025-3518/"}