{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-20120 exists.","fix":"No fix has been published for CVE-2010-20120 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-20120 is a high-severity code injection vulnerability in Maplesoft Maple, published on 21 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2010-20120 and fix it if it is affected.\n\nWhat it is: CVE-2010-20120 is a high-severity code injection vulnerability in Maplesoft Maple, published on 21 Aug 2025. It can only be exploited from the same machine or local 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-2010-20120 exists.\n\nAffected product: Maplesoft Maple. 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-2010-20120/ (Markdown: https://insights.sbomify.com/CVE-2010-20120/index.md)","id":"CVE-2010-20120","markdown":"https://insights.sbomify.com/CVE-2010-20120/index.md","name":"CVE-2010-20120","record":{"aliases":["GHSA-m5v7-vw94-qc72"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Maple mathematical software","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious .maplet files, bypassing Maple's standard security restrictions.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Maple versions up to and including 13's Maplet framework allows embedded commands to be executed automatically when a .maplet file is opened. This behavior bypasses standard security restrictions that normally prevent code execution in regular Maple worksheets. The vulnerability enables attackers to craft malicious .maplet files that execute arbitrary code without user interaction.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2010-04-26","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2010-04-26","kind":"metasploit","ref":"exploit/multi/fileformat/maple_maplet","stars":null,"title":"Maple Maplet File Creation and Command Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Maple \u003c= v13 Maplet File Creation and Command Execution","id":"CVE-2010-20120","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2010"},"n_packages":0,"n_references":5,"next":{"headline":"EasyFTP Server \u003c= 1.7.0.11 CWD Command Stack Buffer Overflow","id":"CVE-2010-20121"},"packages":[],"prev":{"headline":"CommuniCrypt Mail \u003c= 1.16 ANSMTP/AOSMTP ActiveX Control Buffer Overflow","id":"CVE-2010-20119"},"products":["Maple"],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["Maplesoft"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious .maplet files, bypassing Maple's standard security restrictions.","url":"https://insights.sbomify.com/CVE-2010-20120/"}