CVE-2018-7090
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 · uneditedHPE XP P9000 Command View Advanced Edition Software (CVAE) has local and remote cross site scripting vulnerability in versions 7.0.0-00 to earlier than 8.60-00 of DevMgr, TSMgr and RepMgr.
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 HPE XP P9000 Command View Advanced Edition Software affecting DevMgr, TSMgr, and RepMgr components in versions 7.0.0-00 through versions earlier than 8.60-00. The vulnerability allows injection of malicious scripts through local and remote attack vectors.
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>= 7.0.0-00, < 8.60-00CVSS 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.
-
Identify HPE XP P9000 Command View versionLocate the installed version of HPE XP P9000 Command View Advanced Edition software. Check the application itself, its installation directory, or the version information accessible through the management interface. Compare the version number against the affected range 7.0.0-00 through versions earlier than 8.60-00.Affected if The installed version falls within 7.0.0-00 to 8.59-xx (anything below 8.60-00).
-
Confirm DevMgr component is accessibleDetermine whether the DevMgr component is enabled and accessible in the HPE XP P9000 Command View environment. This may be visible in the web interface, component listings, or configuration settings.Affected if DevMgr is present and the version is in the affected range.
-
Confirm TSMgr component is accessibleDetermine whether the TSMgr component is enabled and accessible in the HPE XP P9000 Command View environment. Check the web interface or component configuration for its presence.Affected if TSMgr is present and the version is in the affected range.
-
Confirm RepMgr component is accessibleDetermine whether the RepMgr component is enabled and accessible in the HPE XP P9000 Command View environment. Verify its status through the management interface or configuration.Affected if RepMgr is present and the version is in the affected range.
The environment is affected if HPE XP P9000 Command View Advanced Edition version is 7.0.0-00 or higher but lower than 8.60-00, and any of the DevMgr, TSMgr, or RepMgr components are accessible.
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 data8.60-00
Upgrade HPE XP P9000 CVAE to version 8.60-00 or later to remediate the XSS vulnerability in all affected components.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7090 — 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-2018-7090 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