ExpeditionApplication · Paloaltonetworks
CVE-2025-0104
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 · uneditedA reflected cross-site scripting (XSS) vulnerability in Palo Alto Networks Expedition enables attackers to execute malicious JavaScript code in the context of an authenticated Expedition user’s browser if that authenticated user clicks a malicious link that allows phishing attacks and could lead to Expedition browser-session theft.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in Palo Alto Networks Expedition allows attackers to inject malicious JavaScript through crafted URLs. When an authenticated user clicks a malicious link, the attacker's script executes in the user's browser context, enabling session hijacking and phishing attacks.
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
ExpeditionApplication
< 1.2.101CVSS 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.1/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.
-
Confirm Expedition is installedCheck for Expedition installation directory, typically at /opt/paloaltonetworks/expedition or look for the 'expedition' service running via 'systemctl list-units | grep expedition' or 'ps aux | grep expedition'Affected if Expedition software is present on the system
-
Identify installed Expedition versionCheck the version file in the Expedition installation directory, commonly found via 'cat /opt/paloaltonetworks/expedition/version' or access the web UI and check the About/Help section for the version numberAffected if Version number is lower than 1.2.101
-
Verify web interface is accessibleTest connectivity to the Expedition web interface on its configured port (default 443) using 'curl -k https://<expedition-ip>/' or by attempting browser accessAffected if Web interface responds and accepts authentication
-
Review access logs for malicious URL patternsExamine Expedition web server logs (typically in /var/log/ or within the Expedition logs directory) for requests containing suspicious patterns like '<script>', 'javascript:', or other XSS vectors in URL parametersAffected if Logs show evidence of XSS payload attempts in URLs
The environment is affected if Expedition version is less than 1.2.101 and the web interface is accessible to authenticated users, since the reflected XSS requires an authenticated session to trigger via crafted URLs.
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.
dbcve · scoped1.2.101
Apply the vendor-supplied patch from Palo Alto Networks; advise users to avoid clicking untrusted links while authenticated to Expedition.
Expedition 1.2.101 or later
- 1. Check current Expedition version by accessing the Expedition web interface or running the command: expedition -v
- 2. Backup all Expedition configurations, migration projects, and settings before proceeding with the upgrade
- 3. Download the Expedition version 1.2.101 or later from the Palo Alto Networks Customer Support Portal
- 4. Upload the upgrade file through the Expedition web interface under Administration > System > Software, or use the CLI if preferred
- 5. Follow the on-screen prompts to complete the upgrade process
- 6. After upgrade completes, verify the version is now 1.2.101 or later using: expedition -v
- 7. Log in and verify Expedition functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0104 — 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-2025-0104 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