CVE-2026-2072
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 · uneditedCross-Site Scripting vulnerability in Hitachi Infrastructure Analytics Advisor (Analytics probe component), Hitachi Ops Center Analyzer.This issue affects Hitachi Infrastructure Analytics Advisor:; Hitachi Ops Center Analyzer: from 10.0.0-00 before 11.0.5-00.
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 the Analytics probe component of Hitachi Infrastructure Analytics Advisor and Hitachi Ops Center Analyzer allows attackers to inject malicious scripts into web pages viewed by other users, potentially leading to session hijacking or credential theft.
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 dataall versions>= 10.0.0-00, < 11.0.5-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.1/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.
-
Confirm Analytics probe component is in useAccess the Hitachi Infrastructure Analytics Advisor or Hitachi Ops Center Analyzer administration console and navigate to the Analytics probe configuration section to verify if the component is enabled or provisioned.Affected if The Analytics probe component is configured or active in the environment
-
Check Hitachi Infrastructure Analytics Advisor versionLocate the installation directory for Hitachi Infrastructure Analytics Advisor and look for a version file, or use the product's built-in version information panel in the admin interface (typically found under Help or About).Affected if The installed version is below 11.0.5-00
-
Check Hitachi Ops Center Analyzer versionLocate the installation directory for Hitachi Ops Center Analyzer and look for a version file, or use the product's built-in version information panel in the admin interface (typically found under Help or About).Affected if The installed version is below 11.0.5-00
A user is affected if either Hitachi Infrastructure Analytics Advisor or Hitachi Ops Center Analyzer is installed with the Analytics probe component enabled and the version is earlier than 11.0.5-00.
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.
dbcve · scoped11.0.5-00
Upgrade Hitachi Infrastructure Analytics Advisor and Hitachi Ops Center Analyzer to version 11.0.5-00 or later to remediate this vulnerability.
11.0.5-00 or later
- Verify current version of Hitachi Infrastructure Analytics Advisor or Hitachi Ops Center Analyzer by checking the application or system documentation
- Contact Hitachi support or refer to official documentation to obtain the upgrade package for version 11.0.5-00 or later
- Follow Hitachi's documented upgrade procedure to update to version 11.0.5-00 or later
- After upgrade, verify the new version is correctly installed and the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2072 — 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-2026-2072 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