CVE-2020-6978
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 · uneditedIn Honeywell WIN-PAK 4.7.2, Web and prior versions, the affected product is vulnerable due to the usage of old jQuery libraries.
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 · moderate confidenceThe Honeywell WIN-PAK 4.7.2 web interface contains outdated jQuery libraries with known vulnerabilities. These older jQuery versions are susceptible to cross-site scripting (XSS) and other client-side attacks, potentially allowing authenticated attackers to execute malicious JavaScript in the context of user sessions.
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< 4.7.2_b1072.3.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed WIN-PAK versionLocate the WIN-PAK installation directory and check version information in the About dialog, installation logs, or version file typically found in the program files folder. On Windows, check Add/Remove Programs or the version info within the WIN-PAK application.Affected if The installed version is lower than 4.7.2_b1072.3.4
-
Verify web interface is enabledConfirm that the WIN-PAK web service or web application is running and accessible. Check Windows Services for WIN-PAK related web services, or attempt to access the web interface URL (commonly http://localhost/WIN-PAK or similar local address).Affected if The web interface is exposed and accessible to users or attackers on the network
-
Inspect jQuery version in useAccess the WIN-PAK web interface in a browser, then view the page source or use browser developer tools to examine the jQuery script tag. Look for jquery-x.x.x.js or similar file references in the HTML. Alternatively, check the web application directory for bundled jQuery library files.Affected if The jQuery version bundled with the installation is a known vulnerable version (typically pre-3.5.0 for XSS issues)
-
Compare against affected rangeDocument the exact version number found in step 1 and the jQuery version from step 3. Compare the WIN-PAK version against the threshold of 4.7.2_b1072.3.4.Affected if WIN-PAK version is below 4.7.2_b1072.3.4 and the web interface is accessible with outdated jQuery
You are affected if your WIN-PAK installation version is lower than 4.7.2_b1072.3.4 and the web interface is enabled, as this indicates bundled outdated jQuery libraries vulnerable to XSS.
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 data4.7.2_b1072.3.4
Update the jQuery libraries in the WIN-PAK web application to a current, supported version that addresses known vulnerabilities. Verify the update does not break existing functionality through regression testing.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6978 — 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-6978 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