Vulnerability

CVE-2012-2539

High· 7.8KEVCVSS7.8EPSS84%

.rules3/5

Microsoft Word Remote Code Execution Vulnerability

Microsoft Word allows attackers to execute remote code or cause a denial-of-service (DoS) via crafted RTF data.

Threat signal

100/100

Severe

Severity

high

CVSS

7.8

EPSS

84%

Active

KEV

CISA KEV — actively exploited

1517d overdue

AffectedMicrosoft — Word

Added to KEV

2022-03-28

Federal patch due (BOD 22-01)

2022-04-18

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2012-2539

CISA description: “Microsoft Word allows attackers to execute remote code or cause a denial-of-service (DoS) via crafted RTF data.”

CVSS

v3.1Open in FIRST calculator →

7.8/ 10HIGHCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack VectorLocalRequires local access — shell, console, or local app.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionRequiredRequires user action (click, file open, etc).
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

84.4%

probability of exploitation in next 30 days

p99

higher than 99% of all CVEs

3-day trend↑ 0pp

Statistically about to be weaponized — top-tier triage urgency.

Vendor VEX

No VEX statements published for CVE-2012-2539. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: no
impact: total
mission: support

Lifecycle

2022-03-28Added to CISA KEVransomware: Unknown
2022-03-28Published
2022-04-18Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.