CVE-2020-1449 json
A remote code execution vulnerability exists in Microsoft Project software when the software fails to check the source markup of a file, ak…
published 6y ago modified 4mo ago also EUVD-2020-12324
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in Microsoft Project software when the software fails to check the source markup of a file, aka 'Microsoft Project Remote Code Execution Vulnerability'.
Patch / fix
Is CVE-2020-1449 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
4.65% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Microsoft Office
- Microsoft Microsoft 365 Apps for Enterprise for 32-bit Systems
- Microsoft Microsoft 365 Apps for Enterprise for 64-bit Systems
- Microsoft Microsoft Project
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1449
patch, vendor-advisory
Sources
- CVE List CVE-2020-1449
- NVD CVE-2020-1449
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.