CyberSecBulletin
CVE-2009-0238Exploited in the wildNVD status: Analyzed

Microsoft Office Remote Code Execution

CVE-2009-0238 is a high-severity improper control of generation of code vulnerability in Excel from Microsoft, with a CVSS 2.0 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Excel versions: 2000; 2002; 2003, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on April 14, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of Excel you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  3. Read the advisory on microsoft.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftExcel2000; 2002; 2003; 2007Not stated
MicrosoftExcel ViewerNot specified in the recordNot stated
MicrosoftOffice2004; 2008Not stated
MicrosoftOffice Compatibility Pack2007Not stated
MicrosoftOffice Excel Viewer2003Not stated

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Access vector
NetworkCan be exploited remotely over a network.
Access complexity
MediumSome conditions must be met.
Authentication
NoneNo login is needed.
Confidentiality
CompleteAll data can be read.
Integrity
CompleteAny data can be modified.
Availability
CompleteThe system can be shut down completely.

Vector: AV:N/AC:M/Au:N/C:C/I:C/A:C. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighCISA (ADP)
CVSS 2.09.3HighNVD

Official description

Microsoft Office Excel 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1; Excel Viewer 2003 Gold and SP3; Excel Viewer; Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1; and Excel in Microsoft Office 2004 and 2008 for Mac allow remote attackers to execute arbitrary code via a crafted Excel document that triggers an access attempt on an invalid object, as exploited in the wild in February 2009 by Trojan.Mdropper.AC.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Control of Generation of Code

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

How developers prevent this class of flaw

  • Refactor your program so that you do not have to dynamically generate code.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

More Improper Control of Generation of Code vulnerabilities (CWE-94)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Other references

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.