CVE-2021-26845
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 · uneditedInformation Exposure vulnerability in Hitachi ABB Power Grids eSOMS allows unauthorized user to gain access to report data if the URL used to access the report is discovered. This issue affects: Hitachi ABB Power Grids eSOMS 6.0 versions prior to 6.0.4.2.2; 6.1 versions prior to 6.1.4; 6.3 versions prior to 6.3.
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 confidenceAn information exposure vulnerability in Hitachi ABB Power Grids eSOMS allows unauthorized users to access report data if the URL to the report is discovered. This indicates a lack of proper authorization controls on the report access endpoint, where the application fails to verify user permissions before serving report content.
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>= 6.0, < 6.0.4.2.2>= 6.1, < 6.1.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Determine the installed eSOMS versionLocate the eSOMS installation and retrieve its version number through the system's about page, version info in the software, or configuration files that contain version metadataAffected if The installed version falls within >= 6.0 and < 6.0.4.2.2, or >= 6.1 and < 6.1.4
-
Identify report access endpointsLocate the report access functionality within the eSOMS application by reviewing the application's URL structure, particularly endpoints that serve report data or allow report downloadsAffected if Report access endpoints exist and are accessible within the application
-
Test unauthorized access to report URLsAttempt to access known report URLs without providing valid authentication credentials or a session token, observing whether the application returns the report content without prompting for loginAffected if Report content is returned without requiring authentication or authorization verification
-
Verify authorization enforcement on report endpointsLog in with a user account that lacks permissions to view specific reports, then attempt to access those report URLs directly to confirm the application validates user permissions before serving contentAffected if Reports are served to users who should not have permission to view them, indicating missing authorization checks
You are affected if your eSOMS version is 6.0.x before 6.0.4.2.2 or 6.1.x before 6.1.4 AND report URLs can be accessed or viewed without proper authentication and authorization validation.
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 data6.0.4.2.26.1.4
Upgrade to the patched versions (6.0.4.2.2, 6.1.4, or 6.3) and implement proper authentication/authorization checks on all report access URLs to ensure only authorized users can view reports.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26845 — 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-2021-26845 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