{"answers":{"affected":"It affects 3 products.","exploited":"Yes. Attackers have exploited CVE-2012-1854 in the wild since at least 13 Apr 2026.","fix":"No fix has been published for CVE-2012-1854 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Apr 2026.","what":"CVE-2012-1854 is a high-severity vulnerability in Microsoft Office, published on 10 Jul 2012. 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-2012-1854 and fix it if it is affected.\n\nWhat it is: CVE-2012-1854 is a high-severity vulnerability in Microsoft Office, published on 10 Jul 2012. 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: Yes. Attackers have exploited CVE-2012-1854 in the wild since at least 13 Apr 2026.\n\nAffected product: Microsoft Office. 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-2012-1854/ (Markdown: https://insights.sbomify.com/CVE-2012-1854/index.md)","id":"CVE-2012-1854","markdown":"https://insights.sbomify.com/CVE-2012-1854/index.md","name":"CVE-2012-1854","record":{"aliases":["GHSA-77fm-4w36-vpp3"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office VBA","requires_auth":"none","summary":"Local attackers can gain privileges via a malicious DLL in the working directory when opening documents in Microsoft Office or VBA.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"},{"product":"visual_basic_for_applications","vendor":"microsoft"},{"product":"visual_basic_for_applications_sdk","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"Untrusted search path vulnerability in VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1; Microsoft Visual Basic for Applications (VBA); and Summit Microsoft Visual Basic for Applications SDK allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a .docx file, aka \"Visual Basic for Applications Insecure Library Loading Vulnerability,\" as exploited in the wild in July 2012.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Microsoft Visual Basic for Applications Insecure Library Loading","id":"CVE-2012-1854","indexable":true,"kev":{"dateAdded":"2026-04-13","dueDate":"2026-04-27","knownRansomwareCampaignUse":"Unknown","product":"Visual Basic for Applications (VBA)","requiredAction":"Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.","vendorProject":"Microsoft","vulnerabilityName":"Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"privilege_escalation","year":"2012"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2012-1855"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2012-1853"},"products":["n/a"],"published":"2012-07-10","related":[{"cvss_score":8.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0798","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":8.8,"headline":"Microsoft Office Uninitialized Memory Use","id":"CVE-2015-1770","kev_date_added":"2022-03-28","published":"2015-06-10"},{"cvss_score":8.8,"headline":"Microsoft Word Malformed Object Pointer","id":"CVE-2006-2492","kev_date_added":"2022-06-08","published":"2006-05-20"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0802","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2017-11882","kev_date_added":"2021-11-03","published":"2017-11-15"},{"cvss_score":7.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2017-8570","kev_date_added":"2022-02-25","published":"2017-07-11"},{"cvss_score":7.8,"headline":"Microsoft Office Use-After-Free","id":"CVE-2017-0261","kev_date_added":"2022-03-03","published":"2017-05-12"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-14","vendors":["n/a"]},"summary":"Local attackers can gain privileges via a malicious DLL in the working directory when opening documents in Microsoft Office or VBA.","url":"https://insights.sbomify.com/CVE-2012-1854/"}