CVE-2021-23874: McAfee Total Protection (MTP) Improper Privilege Management
McAfee Total Protection (MTP) · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 8.2
- high
- EPSS (exploit probability, 30 days)
- 1.1%
- higher than 65.7% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2021-11-17
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2021-23874 explained
CVE-2021-23874 is an arbitrary process execution flaw in McAfee Total Protection (MTP) for Windows before 16.0.30. A local user can gain elevated privileges and run arbitrary code while bypassing MTP self-defense. CISA lists it as known exploited, so affected systems should be updated promptly.
Impact
An attacker with low-privileged local access can escalate privileges and execute arbitrary code, bypassing the product's self-defense protections. User interaction is required, and the scope is changed, so the impact reaches beyond the vulnerable component. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total but not automatable. It is in CISA's Known Exploited Vulnerabilities catalog, so attackers are known to use it.
Who is affected
McAfee,LLC McAfee Total Protection (MTP) on Windows is affected in all versions before 16.0.30 (< 16.0.30). The CVE record names 16.0.30 as the fixed version. These details come from the CVE record published by its CNA (trellix).
Written with AI from the data on this page and checked against it automatically.
Official description
Arbitrary Process Execution vulnerability in McAfee Total Protection (MTP) prior to 16.0.30 allows a local user to gain elevated privileges and execute arbitrary code bypassing MTP self-defense.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- McAfee,LLC McAfee Total Protection (MTP)WindowsAffectedFixed in
- < 16.0.30
- 16.0.30
| Product | Affected | Fixed in |
|---|---|---|
| McAfee,LLC McAfee Total Protection (MTP)Windows |
|
|
How to fix it
- Update to a fixed version: 16.0.30.
- Vendor advisory: service.mcafee.com/FAQDocument.aspx
- CISA's deadline for US federal agencies: 2021-11-17 (passed) – a useful benchmark for everyone else, too.
What to do
- Update McAfee Total Protection (MTP) on all Windows systems to
16.0.30or later. - Follow the vendor advisory and apply updates per vendor instructions, as CISA requires.
- Verify that every endpoint reports the fixed version after updating.
- Limit local access and use least-privilege accounts on systems running MTP.
- Check systems that ran vulnerable versions for signs of compromise or unexpected privileged processes.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-269 Improper Privilege Management
Questions about CVE-2021-23874
- Is CVE-2021-23874 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2021-11-17. Whether it has been used in ransomware campaigns is unknown.
- Can it be exploited remotely?
- No. The attack vector is local. An attacker needs low-privileged access to the system, and user interaction is required. CISA rates it as not automatable.
- Which version fixes the issue?
- The CVE record names
16.0.30as the fixed version. All McAfee Total Protection (MTP) versions before16.0.30on Windows are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.