CVE-2020-26869
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 · uneditedARC Informatique PcVue prior to version 12.0.17 is vulnerable to information exposure, allowing unauthorized users to access session data of legitimate users. This issue also affects third-party systems based on the Web Services Toolkit.
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 confidenceARC Informatique PcVue before version 12.0.17 contains an information exposure vulnerability that allows unauthorized users to access session data of legitimate users. This flaw enables potential session hijacking as attacker(s) can obtain valid session credentials. The vulnerability also impacts third-party systems built on the Web Services Toolkit.
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>= 8.10, < 12.0.17CVSS 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.
-
Verify PcVue installationCheck for PcVue installation directories (commonly in C:\Program Files\Arcinfo or C:\Program Files (x86)\Arcinfo) or query Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for PcVue entriesAffected if PcVue software is found on the system
-
Determine installed PcVue versionLocate version information in the installation folder (typically in version.dll, about dialog, or check file properties of main executable pcvue.exe), or query registry keys if availableAffected if Installed version is 8.10 or higher but lower than 12.0.17
-
Identify Web Services Toolkit usageSearch for Web Services Toolkit components in the installation directory or examine application configuration files that reference Web Services or WSDL-based servicesAffected if Third-party systems built on Web Services Toolkit are deployed using the affected PcVue installation
You are affected if PcVue version is 8.10 or newer but older than 12.0.17, or if third-party systems using Web Services Toolkit share this environment.
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 data12.0.17
Upgrade PcVue to version 12.0.17 or later to remediate this vulnerability. Organizations using third-party systems based on the Web Services Toolkit should contact vendors for patched versions.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26869 — 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-2020-26869 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