{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64319 is a medium-severity missing authorization vulnerability in Salesforce Mulesoft Anypoint Code Builder, published on 4 Nov 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-64319 and fix it if it is affected.\n\nWhat it is: CVE-2025-64319 is a medium-severity missing authorization vulnerability in Salesforce Mulesoft Anypoint Code Builder, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64319 in the wild and no public exploit code.\n\nAffected product: Salesforce Mulesoft Anypoint Code Builder. 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-64319/ (Markdown: https://insights.sbomify.com/CVE-2025-64319/index.md)","id":"CVE-2025-64319","markdown":"https://insights.sbomify.com/CVE-2025-64319/index.md","name":"CVE-2025-64319","record":{"aliases":["GHSA-4c2j-p6fq-fm4p"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Mulesoft Anypoint Code Builder","requires_auth":"none","summary":"Attackers can manipulate writable configuration files due to incorrect permission assignments in Mulesoft Anypoint Code Builder.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Salesforce","cpe":[{"product":"mulesoft_anypoint_code_builder","vendor":"salesforce"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Incorrect Permission Assignment for Critical Resource vulnerability in Salesforce Mulesoft Anypoint Code Builder allows Manipulating Writeable Configuration Files.This issue affects Mulesoft Anypoint Code Builder: before 1.12.1","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":"Missing authorization in Mulesoft Anypoint Code Builder","id":"CVE-2025-64319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in Agentforce Vibes Extension","id":"CVE-2025-64320"},"packages":[],"prev":{"headline":"Code injection in Mulesoft Anypoint Code Builder","id":"CVE-2025-64318"},"products":["Mulesoft Anypoint Code Builder"],"published":"2025-11-04","related":[{"cvss_score":6.5,"headline":"Code injection in Mulesoft Anypoint Code Builder","id":"CVE-2025-10875","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":5.3,"headline":"Code injection in Mulesoft Anypoint Code Builder","id":"CVE-2025-64318","kev_date_added":null,"published":"2025-11-04"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-11","vendors":["Salesforce"]},"summary":"Attackers can manipulate writable configuration files due to incorrect permission assignments in Mulesoft Anypoint Code Builder.","url":"https://insights.sbomify.com/CVE-2025-64319/"}