No. A PHP vulnerability does not affect portier Vision 5, whether it reaches you as a CVE number or as an advisory from a security agency such as the BSI.
What portier Vision 5 is built on
portier Vision 5 is a Windows application. Its data sits in a Firebird or Microsoft SQL Server database. PHP is neither used nor shipped, not in the portier Vision Companion and not in any file the installer brings with it. portier Vision 5 needs no PHP on your servers.
If your scanner finds PHP on the server that runs portier Vision 5, it belongs to another application.
Check it yourself
Since version 5.8.2 the installation folder holds a machine-readable component list in CycloneDX format, the file THIRD_PARTY_SBOM-<version>.cdx.json. Your IT team can load it into its own vulnerability scanner and see for itself, at the next advisory, whether any component of portier Vision 5 is affected.
What about portier Vision 4?
portier Vision 4 contains no PHP either. It is no longer supported, though, and receives no security updates. portier Vision 5 has, among other things, improved its protection against SQL injection, the way passwords are stored and the encryption of licence and connection data. None of these fixes exists for version 4.
We therefore recommend moving to portier Vision 5. The background is in Why is operating portier Vision 4 (End-of-Life) no longer GDPR-, KRITIS-, DORA- and NIS-2-compliant?, and the move step by step in Upgrading to portier Vision 5 with Firebird migration and MS SQL Server.
Have a specific advisory checked
Write to [email protected] with the CVE number or advisory reference and your installed version, and we will check the advisory against your installation.
portier is certified to ISO/IEC 27001:2022. The certificate and further evidence are in the Trust Center at trust.portierglobal.com.