CVE-2023-45796
Stored XSS in Pilz PASvisu Runtime; unauthenticated attacker can alter process data.
Is CVE-2023-45796 being exploited?
Not confirmed. CVE-2023-45796 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.
How severe is CVE-2023-45796?
CVE-2023-45796 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2023-45796?
Yes. A fix has been recorded for CVE-2023-45796. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2023-45796 affect?
CVE-2023-45796 affects Pilz PASvisu < 1.14.1 (Runtime), Pilz PMI v8xx <= 2.0.33992. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2023-45796?
Patch to PASvisu 1.14.1+ or PMI 2.0.33992+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS enables manipulation of process data, risking integrity and availability.
Patch when possible
- affected< 1.14.1
- affected<= 2.0.33992
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.