dbcve.org
Epolicy OrchestratorApplication · Mcafee

CVE-2018-6659

MEDIUM · 5.4 CVSS v3.0 Published 2018-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Reflected Cross-Site Scripting vulnerability in McAfee ePolicy Orchestrator (ePO) 5.3.2, 5.3.1, 5.3.0 and 5.9.0 allows remote authenticated users to exploit an XSS issue via not sanitizing the user input.

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 confidence

Reflected Cross-Site Scripting (XSS) vulnerability in McAfee ePolicy Orchestrator web interface. User-supplied input in certain parameters is not properly sanitized before being reflected back in the HTTP response, allowing authenticated attackers to inject malicious JavaScript code that executes in the context of other users' browsers.

MitigationApply vendor patch or upgrade to a patched version of ePO. Implement proper input validation and output encoding for all user-supplied data in web pages.

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
Epolicy OrchestratorApplication
Affected:= 5.3.0= 5.3.1= 5.3.2= 5.9.0

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ePO version
    Access the ePolicy Orchestrator console or check the ePO installation directory for version information. Typically found in the About section of the ePO console or in installation logs.
    Affected if The installed version matches exactly 5.3.0, 5.3.1, 5.3.2, or 5.9.0
  2. Confirm web interface is enabled
    Verify that the ePO web interface (ePO console) is accessible and operational. This is typically accessible on port 8443 or 443.
    Affected if The ePO web console is accessible and the installed version is one of the affected versions listed above
  3. Verify authentication configuration
    Check whether authentication is required and enabled for accessing the ePO web interface. Reflected XSS requires a user to be authenticated.
    Affected if The web interface is accessible with authentication enabled and the ePO version is among the affected versions

A user is affected if they are running ePO versions 5.3.0, 5.3.1, 5.3.2, or 5.9.0 with the web interface accessible and authentication enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or upgrade to a patched version of ePO. Implement proper input validation and output encoding for all user-supplied data in web pages.

Fix this in Epolicy Orchestrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-6659 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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