Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2010-3141: DLL Hijacking in Microsoft PowerPoint 2010

Published Aug 27, 2010 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS15.4%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2010-3141CWE-427

CVE-2010-3141 describes an untrusted search path vulnerability in Microsoft PowerPoint 2010. The application searches for and loads pptimpconv.dll from the directory containing a PowerPoint file (.odp, .pot, .potm, .potx, .ppa, .pps, .ppsm, .ppsx, .ppt, .pptm, .pptx, .pwz, .sldm, or .sldx) before searching trusted system directories. An attacker can exploit this by placing a malicious pptimpconv.dll in the same directory as a PowerPoint file, leading to arbitrary code execution when the file is opened.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows local users, and potentially remote attackers (via network shares or extracted archives), to execute arbitrary code in the context of the user running PowerPoint. This can lead to full compromise of the affected system, depending on user privileges.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, avoid opening PowerPoint files from directories containing untrusted files, especially DLLs. Use file system permissions to restrict write access to directories where PowerPoint files are stored. Consider using tools such as Microsoft Sysinternals Process Monitor to detect suspicious DLL loading behavior.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft that address the untrusted search path issue by ensuring PowerPoint only loads DLLs from trusted locations. Avoid opening PowerPoint files from untrusted directories or network shares until patched.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationPowerpointapplication
FAQ

Frequently asked questions

Is CVE-2010-3141 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-3141 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-3141?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2010-3141.
Is there a patch for CVE-2010-3141?
Apply the security updates provided by Microsoft that address the untrusted search path issue by ensuring PowerPoint only loads DLLs from trusted locations. Avoid opening PowerPoint files from untrusted directories or network shares until patched.
What products are affected by CVE-2010-3141?
Microsoft Corporation Powerpoint.
How severe is CVE-2010-3141?
CVE-2010-3141 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 15.4% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.