CVE-2019-3591
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ePO extension in McAfee Data Loss Prevention (DLPe) for Windows 11.x prior to 11.3.0 allows unauthenticated remote user to trigger specially crafted JavaScript to render in the ePO UI via a carefully crafted upload to a remote website which is correctly blocked by DLPe Web Protection. This would then render as an XSS when the DLP Admin viewed the event in the ePO UI.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in McAfee Data Loss Prevention (DLPe) ePO extension allows unauthenticated remote attackers to inject malicious JavaScript. The attack occurs when a user uploads specially crafted content to a remote website; DLPe Web Protection blocks the content, but when a DLP Administrator views the blocked event in the ePO UI, the embedded JavaScript executes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 11.0, < 11.1.200>= 11.2.000, < 11.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify McAfee DLPe installationCheck Windows Registry under HKLM\SOFTWARE\McAfee\DLPe or view installed programs in Control Panel to confirm Data Loss Prevention Endpoint is installedAffected if DLPe is not installed on the system
-
Identify DLPe version from local installationCheck registry key HKLM\SOFTWARE\McAfee\DLPe\CurrentVersion or examine the DLPe agent version displayed in the system tray or McAfee agent consoleAffected if The version displayed cannot be determined or does not match the ePO extension version
-
Check ePO console for DLPe extension versionLog into the ePO console, navigate to Menu > Software > Products, locate McAfee Data Loss Prevention, and record the installed versionAffected if DLPe ePO extension version cannot be determined from the console
-
Compare version against affected rangesCompare the identified DLPe version to the affected ranges: 11.0.0 through 11.1.199, or 11.2.000 through 11.2.x (any version below 11.3.0)Affected if The installed version falls within >= 11.0, < 11.1.200 OR >= 11.2.000, < 11.3.0
A system is affected if McAfee Data Loss Prevention Endpoint with an ePO extension version is present and that version falls within 11.0 to 11.1.199 or 11.2.000 to 11.2.x (anything below 11.3.0).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data11.1.20011.3.0
Upgrade McAfee Data Loss Prevention (DLPe) for Windows to version 11.3.0 or later to resolve the XSS vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3591 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3591 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data