CVE-2020-7574
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 · uneditedA vulnerability has been identified in Climatix POL908 (BACnet/IP module) (All versions), Climatix POL909 (AWM module) (All versions < V11.32). A persistent cross-site scripting (XSS) vulnerability exists in the "Server Config" web interface of the affected devices that could allow an attacker to inject arbitrary JavaScript code. The code could be potentially executed later by another (possibly privileged) user. The security vulnerability could be exploited by an attacker with network access to the affected system. Successful exploitation requires no system privileges. An attacker could use the vulnerability to compromise the confidentiality and integrity of other users' web session.
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 confidenceA persistent/stored cross-site scripting (XSS) vulnerability exists in the Server Config web interface of Climatix POL908 (BACnet/IP module) and POL909 (AWM module) devices. Attackers with network access can inject malicious JavaScript code into the Server Config functionality, which gets stored on the device. When other users later access the Server Config page, the injected script executes in their browsers, enabling session hijacking and data 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< 11.32CVSS 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.
-
Identify the Climatix module modelLocate the device label or access the web interface to confirm whether the unit is POL908 (BACnet/IP module) or POL909 (AWM module). This determines which version criteria apply.Affected if The device is a POL908 (all versions affected) or POL909 with firmware < 11.32.
-
Check the installed firmware versionAccess the Climatix web interface or use the device's administrative console to view the firmware version information. Compare this version number against the affected ranges: POL908 has no safe version (all versions affected); POL909 is affected if version is below 11.32.Affected if Firmware version is unknown, not documented, or falls below 11.32 for POL909.
-
Confirm Server Config web interface is enabledLog into the Climatix web interface and navigate to the Server Config functionality. Verify whether this feature is present and accessible. The vulnerability exists specifically within this Server Config page.Affected if The Server Config interface is accessible and operational on the device.
-
Assess network accessibility of the web interfaceDetermine whether the Climatix web interface (including Server Config) is reachable from network segments outside the trusted internal network. Check firewall rules, NAT configurations, or direct IP accessibility.Affected if The web interface is exposed to untrusted networks or the internet, allowing external attackers to inject malicious script.
A user is affected if they have a POL908 (any version) or POL909 (version < 11.32) device with the Server Config web interface enabled and accessible, particularly if exposed to untrusted networks.
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 data11.32
Apply vendor firmware update V11.32 or later for POL909 devices. For POL908 (all versions), implement network segmentation to limit exposure and consider compensating controls such as web application firewalls, as no fixed version was specified. Validate all user input in the Server Config interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7574 — 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-7574 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