CVE-2019-0863: An elevation of privilege vulnerability exists in the way Windows Error Reporting (WER) handles files, aka 'Windows Error Reporting…
Noroxi assessment
Priority: This week (action score 63/100)
- CISA has confirmed exploitation in the wild (Nov 3, 2021). Remediation deadline for US federal agencies: May 3, 2022.
- Probability of exploitation in the next 30 days: 5.2% (FIRST EPSS); higher than 92.6% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
An elevation of privilege vulnerability exists in the way Windows Error Reporting (WER) handles files, aka 'Windows Error Reporting Elevation of Privilege Vulnerability'.
- Published
- May 16, 2019
- Updated
- Jun 16, 2026
- EPSS
- 5.2% · 92th percentile
- CWE
- —
Report tools
Action score
63
Don’t wait for the next maintenance window.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 2 / 30 · 5.2%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Nov 3, 2021. That signals real attacks, not theory.
Remediation deadline for US federal agencies: May 3, 2022.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1703 | cpe:2.3:o:microsoft:windows_10_1703 |
| microsoft | windows 10 1709 | cpe:2.3:o:microsoft:windows_10_1709 |
| microsoft | windows 10 1803 | cpe:2.3:o:microsoft:windows_10_1803 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 1903 | cpe:2.3:o:microsoft:windows_10_1903 |
| microsoft | windows 7 | cpe:2.3:o:microsoft:windows_7 |
| microsoft | windows 8.1 | cpe:2.3:o:microsoft:windows_8.1 |
| microsoft | windows rt 8.1 | cpe:2.3:o:microsoft:windows_rt_8.1 |
| microsoft | windows server 1803 | cpe:2.3:o:microsoft:windows_server_1803 |
| microsoft | windows server 1903 | cpe:2.3:o:microsoft:windows_server_1903 |
and 4 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows
- 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 10 Version 1703 for 32-bit Systems, 10 Version 1703 for x64-based Systems, 10 Version 1709 for 32-bit Systems … (+8)affected
Microsoft Windows 10 Version 1903 for 32-bit Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1903 for ARM64-based Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1903 for x64-based Systems
- unspecifiedaffected
Microsoft Windows Server
- 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation), 2016, 2016 (Core installation), version 1803 (Core Installation), 2019, 2019 (Core installation)affected
Microsoft Windows Server, version 1903 (Server Core installation)
- unspecifiedaffected
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 1803all versions
- microsoft windows server 1903all versions
- microsoft windows server 2008r2
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016all versions
- microsoft windows server 2019all versions
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34527Windows Print Spooler Remote Code Execution VulnerabilityKEV95Now
- CVE-2021-40444Microsoft MSHTML Remote Code Execution VulnerabilityKEV94Now
- CVE-2023-36025Windows SmartScreen Security Feature Bypass VulnerabilityKEV92Now
Published before and after this one in the same product
- ← EarlierCVE-2019-0803Apr 9, 2019 · An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k…KEV75This week
- ← EarlierCVE-2019-0859Apr 9, 2019 · An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k…KEV62This week
- Later →CVE-2019-0903May 16, 2019 · A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory, aka…KEV72This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2019-05-22 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+5 d
- CISA KEV+901 d
- TodayNov 16, 2026+2741 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.