Pan OsOperating system · Paloaltonetworks
CVE-2018-7636
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 · uneditedThe URL filtering "continue page" hosted by PAN-OS 8.0.10 and earlier may allow an attacker to inject arbitrary JavaScript or HTML via specially crafted URLs.
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 confidenceThe URL filtering 'continue page' in PAN-OS 8.0.10 and earlier contains a reflected cross-site scripting (XSS) vulnerability. An attacker can inject arbitrary JavaScript or HTML into the continue page through specially crafted URLs, potentially allowing session hijacking or phishing attacks against users who interact with filtered URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Pan OsOperating system
= 8.0.10CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Determine the installed PAN-OS versionLog into the PAN-OS web interface and navigate to Device > Setup > Operations menu, or use the CLI command 'show system info' to retrieve the current PAN-OS version numberAffected if The displayed version is 8.0.10 or any version earlier than 8.0.11 (e.g., 8.0.9, 8.0.8, 8.0.7, etc.)
-
Verify URL filtering is enabledIn the PAN-OS web interface, go to Objects > URL Filtering and confirm whether a URL filtering profile exists and is attached to a security policy, or use the CLI command 'show url-filtering'Affected if A URL filtering profile is configured and actively applied to security rules
-
Identify if the continue page is in useReview the URL filtering profile settings under the 'Action' tab and check if the 'continue' action is configured for any URL categories, which causes users to see the continue page before being allowed to proceedAffected if The continue page action is assigned to any URL category in the active URL filtering profile
-
Review recent URL filtering logsUse the PAN-OS logs or Monitor > Logs > URL Filtering to search for entries showing the 'continue' action, which indicates the vulnerable page is being served to usersAffected if Recent logs show entries with 'continue' as the action for blocked or filtered URLs
A user is affected if their PAN-OS version is 8.0.10 or earlier AND the URL filtering continue page feature is actively configured and in use.
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.
From vendor dataUpgrade PAN-OS to version 8.0.11 or later, or apply the relevant hotfixes provided by Palo Alto Networks to address this vulnerability.
Fix this in Pan Os
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7636 — 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-2018-7636 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