{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-22389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-22389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22389 is a high-severity vulnerability in n/a, published on 4 Jan 2025. 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-2025-22389 and fix it if it is affected.\n\nWhat it is: CVE-2025-22389 is a high-severity vulnerability in n/a, published on 4 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-22389 in the wild and no public exploit code.\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-22389/ (Markdown: https://insights.sbomify.com/CVE-2025-22389/index.md)","id":"CVE-2025-22389","markdown":"https://insights.sbomify.com/CVE-2025-22389/index.md","name":"CVE-2025-22389","record":{"aliases":["GHSA-fc9r-7hhq-7wqj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Optimizely CMS","requires_auth":"low_privilege","summary":"Attackers can upload malicious files to the CMS, leading to code execution or user system compromise when accessed.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"optimizely_cms","vendor":"optimizely"}],"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":"An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0. A medium-severity vulnerability exists in the CMS, where the application does not properly validate uploaded files. This allows the upload of potentially malicious file types, including .docm .html. When accessed by application users, these files can be used to execute malicious actions or compromise users' systems.","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 in n/a","id":"CVE-2025-22389","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":"Weak cryptography in n/a","id":"CVE-2025-22390"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-22388"},"products":["n/a"],"published":"2025-01-04","related":[{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2025-22390","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":5.7,"headline":"Cross-site scripting in n/a","id":"CVE-2025-22388","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2023-31754","kev_date_added":null,"published":"2023-11-14"}],"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":"total"},"state":"PUBLISHED","updated":"2025-02-11","vendors":["n/a"]},"summary":"Attackers can upload malicious files to the CMS, leading to code execution or user system compromise when accessed.","url":"https://insights.sbomify.com/CVE-2025-22389/"}