CVE-2023-32652
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 · uneditedPiiGAB M-Bus does not validate identification strings before processing, which could make it vulnerable to cross-site scripting attacks.
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 confidencePiiGAB M-Bus gateway产品存在存储型XSS漏洞，原因是系统在处理标识字符串前未对其进行验证。攻击者可通过在标识符字段中注入恶意脚本代码，当其他用户查看或处理该数据时触发跨站脚本执行。
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 versionsCVSS 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 Piigab M Bus 900s gateway is in useIdentify the deployed M-Bus gateway device model through device inventory, network scanning for the device's hostname or MAC vendor information, or physical device labelingAffected if The environment contains a Piigab M Bus 900s device on the network
-
Identify accessible identifier configuration interfacesLocate the web interface, API endpoint, or configuration tool used to set or modify identifier strings on the Piigab device. This is typically found in the device's administration panel under network settings, device configuration, or M-Bus parameter setupAffected if An administrative or user-accessible interface exists for configuring identifiers
-
Verify identifier input accepts arbitrary character stringsTest whether the identifier field accepts special characters including <, >, ", ', and script tags as input without immediate rejection or sanitization feedbackAffected if The system accepts and stores special characters in the identifier field without validation errors
-
Check if stored identifiers are rendered without encodingAttempt to retrieve or view the stored identifier value through the device's status page, monitoring dashboard, or API response. Examine if raw identifier data is displayed in HTML context without being entity-encodedAffected if Stored identifier values are displayed in the web interface or API responses without HTML entity encoding (e.g., raw <script> tags appear in the output)
If a Piigab M Bus 900s device is present and its identifier fields accept and display unsanitized input containing script tags or HTML characters, the environment is affected by this stored XSS vulnerability.
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 data在所有用户输入的标识字符串进入系统或展示给用户前实现严格的输入验证和输出编码，并结合内容安全策略(CSP)额外防护。
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32652 — 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-2023-32652 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