CVE-2023-45795
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 cross-site scripting vulnerability in the Builder Component of Pilz PASvisu before 1.14.1 allows a local unauthenticated attacker to inject malicious javascript and gain full control over the device.
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 cross-site scripting (XSS) vulnerability exists in the Builder Component of Pilz PASvisu visualization software versions prior to 1.14.1. A local unauthenticated attacker can inject malicious JavaScript code through unsanitized input in the Builder Component, potentially achieving full device control.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Confirm Pilz PASvisu installationLocate the Pilz PASvisu visualization software on the system. Check common software installation directories, program files, or use system inventory tools to identify if PASvisu is present.Affected if Pilz PASvisu is found on the system
-
Identify installed versionDetermine the exact version number of the installed Pilz PASvisu software. Look in the software's about section, installation directory for version files, or use system inventory/management tools that report installed software versions.Affected if Version cannot be determined or is prior to 1.14.1
-
Compare version to affected rangeCompare the identified version number against the affected range: versions prior to 1.14.1. Any version below 1.14.1 falls within the vulnerable range.Affected if Installed version is below 1.14.1 (for example, 1.14.0, 1.13.x, 1.12.x, etc.)
-
Verify Builder Component accessibilityCheck if the Builder Component of PASvisu is accessible or enabled. The vulnerability exists specifically in the Builder Component, so confirm whether this component is available to users.Affected if Builder Component is accessible and version is below 1.14.1
The environment is affected if Pilz PASvisu is installed with a version prior to 1.14.1 and the Builder Component is accessible.
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.
dbcve · scopedUpgrade Pilz PASvisu to version 1.14.1 or later to obtain the security patch for this XSS vulnerability.
Pilz PASvisu version 1.14.1 or later
- 1. Identify the current version of Pilz PASvisu installed on the system
- 2. Download Pilz PASvisu version 1.14.1 or later from the official Pilz website or their support portal
- 3. Review the release notes for version 1.14.1 to understand any changes or requirements
- 4. Create a complete backup of the current PASvisu configuration and project files
- 5. Stop all running PASvisu services before performing the upgrade
- 6. Install version 1.14.1 or the latest available stable version
- 7. Verify the upgrade was successful by checking the installed version number
- 8. Test the Builder Component functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45795 — 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-45795 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