CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2025-0108 remediation guide

Palo Alto Networks PAN-OS

An authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web interface and invoke certain PHP scripts. While invoking these PHP scripts does not enable remote code execution, it can negatively impact integrity and confidentiality of PAN-OS. You can greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practices dep...

Open CVE record
ProductPalo Alto Networks PAN-OS
Affected versions10.1.0, 10.2.0, 11.1.0, 11.2.0, >= 10.1.0 < 10.1.14, >= 10.2.0 < 10.2.7, >= 11.1.0 < 11.1.2, >= 11.2.0 < 11.2.4, 10.1.14, 10.2.7, 10.2.8, 10.2.9, 10.2.10, 10.2.11, 10.2.12, 10.2.13, 11.1.2, 11.1.3, 11.1.4, 11.1.5
Fixed versions10.1.14, 10.2.7, 11.1.2, 11.2.4
Priority basisImmediate · CVSS 8.8 · EPSS 98.5%
01

Identify the affected asset

Confirm whether Palo Alto Networks PAN-OS is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 10.1.0, 10.2.0, 11.1.0, 11.2.0, >= 10.1.0 < 10.1.14, >= 10.2.0 < 10.2.7, >= 11.1.0 < 11.1.2, >= 11.2.0 < 11.2.4, 10.1.14, 10.2.7, 10.2.8, 10.2.9, 10.2.10, 10.2.11, 10.2.12, 10.2.13, 11.1.2, 11.1.3, 11.1.4, 11.1.5. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2025-0108 Remediation Guide | SECUFOCUS NOW