CVE-2023-45796
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 stored cross-site scripting vulnerability in the Runtime component of Pilz PASvisu before 1.14.1 and PMI v8xx up to and including 2.0.33992 allows a low-privileged remote unauthenticated attacker to manipulate process data with potential impact on integrity and/or availability.
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 confidenceStored cross-site scripting (XSS) vulnerability in the Runtime component of Pilz PASvisu (visualization software) and PMI v8xx (industrial operator panels). A low-privileged remote unauthenticated attacker can inject malicious scripts into process data that gets stored and executed when viewed by other users, allowing manipulation of process data impacting integrity and availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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 Pilz visualization productLocate PASvisu or PMI v8xx software on the system by checking installed programs, program files directories, or documentation. Look for Pilz PASvisu or PMI v8xx in the system inventory or registry.Affected if Either PASvisu or PMI v8xx is installed and the version is below 1.14.1 for PASvisu or 2.0.33992 for PMI v8xx
-
Determine PASvisu versionCheck the installed version of PASvisu through the software's about dialog, installation directory, or system registry. Compare the found version to 1.14.1.Affected if Version is present and is below 1.14.1
-
Determine PMI v8xx firmware versionCheck the firmware version of the PMI v8xx operator panel through its web interface, system information menu, or documentation. Compare the found version to 2.0.33992.Affected if Firmware version is present and is 2.0.33992 or earlier
-
Verify Runtime component exposureCheck if the PASvisu Runtime web interface or service is accessible from the network. Look for open ports (typically 80/443 for web-based Runtime) and verify if authentication is required for access.Affected if The Runtime component is network-accessible without requiring authentication or uses weak authentication controls
-
Check for unauthenticated process data accessExamine whether the Runtime allows unauthenticated or low-privileged users to write process data that gets displayed to other users. Review user role configurations and access control settings.Affected if Unauthenticated or low-privileged users can inject data that gets stored and displayed to other users without sanitization
You are affected if either PASvisu below version 1.14.1 or PMI v8xx at firmware 2.0.33992 or earlier is installed, and the Runtime component is accessible allowing unauthenticated or low-privileged users to inject stored script content into process data.
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 dataUpdate PASvisu to version 1.14.1 or later, and update PMI v8xx to a version beyond 2.0.33992. Additionally, implement proper input validation, output encoding, and consider network segmentation to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45796 — 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-45796 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