# CVE-2025-0133: PAN-OS: Reflected Cross-Site Scripting (XSS) Vulnerability in GlobalProtect Gateway and Portal > Reflected XSS in PAN-OS GlobalProtect allows attackers to steal credentials via phishing links, particularly affecting users with Clientless VPN enabled. - **Severity:** Low 1.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/U:Amber`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 14 May 2025 - **Updated:** 2 Apr 2026 - **Also known as:** GHSA-r93p-9jjr-wjhj ## What is CVE-2025-0133? CVE-2025-0133 is a low-severity cross-site scripting vulnerability in Palo Alto Networks Cloud NGFW, published on 14 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A reflected cross-site scripting (XSS) vulnerability in the GlobalProtect™ gateway and portal features of Palo Alto Networks PAN-OS® software enables execution of malicious JavaScript in the context of an authenticated Captive Portal user's browser when they click on a specially crafted link. The primary risk is phishing attacks that can lead to credential theft—particularly if you enabled Clientless VPN. There is no availability impact to GlobalProtect features or GlobalProtect users. Attackers cannot use this vulnerability to tamper with or modify contents or configurations of the GlobalProtect portal or gateways. The integrity impact of this vulnerability is limited to enabling an attacker to create phishing and credential-stealing links that appear to be hosted on the GlobalProtect portal. For GlobalProtect users with Clientless VPN enabled, there is a limited impact on confidentiality due to inherent risks of Clientless VPN that facilitate credential theft. You can read more about this risk in the informational bulletin PAN-SA-2025-0005 https://security.paloaltonetworks.com/PAN-SA-2025-0005 https://security.paloaltonetworks.com/PAN-SA-2025-0005 . There is no impact to confidentiality for GlobalProtect users if you did not enable (or you disable) Clientless VPN. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-0133? ## How do I fix CVE-2025-0133? No fix has been published for CVE-2025-0133 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-0133 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0133 exists. Public exploit code: - CVE-2025-0133 GlobalProtect XSS (github_poc): https://github.com/ynsmroztas/-CVE-2025-0133-GlobalProtect-XSS - Reflected XSS vulnerability found in Palo Alto GlobalProtect Gateway & Portal. Attackers can inject malicious scripts via crafted requests. (github_poc): https://github.com/Inteleon404/CVE-2025-0133 - https://github.com/dodiorne/cve-2025-0133 (github_poc): https://github.com/dodiorne/cve-2025-0133 - CVE-2025-0133 Scanner | Palo Alto GlobalProtect XSS Checker (github_poc): https://github.com/radityahack/cve-2025-0133 - Palo Alto - Global Protect - Reflected XSS (github_poc): https://github.com/wiseep/CVE-2025-0133 - https://github.com/shawarkhanethicalhacker/CVE-2025-0133-exploit (github_poc): https://github.com/shawarkhanethicalhacker/CVE-2025-0133-exploit ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-0133 and fix it if it is affected. What it is: CVE-2025-0133 is a low-severity cross-site scripting vulnerability in Palo Alto Networks Cloud NGFW, published on 14 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0133 exists. Affected product: Palo Alto Networks Cloud NGFW. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-0133/ (Markdown: https://insights.sbomify.com/CVE-2025-0133/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0133 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0133 - OSV: https://osv.dev/vulnerability/CVE-2025-0133 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-0133/ Summaries are generated and may contain mistakes; the official description above is the record.