ExpeditionApplication · Paloaltonetworks
CVE-2025-0107
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 · uneditedAn OS command injection vulnerability in Palo Alto Networks Expedition enables an unauthenticated attacker to run arbitrary OS commands as the www-data user in Expedition, which results in the disclosure of usernames, cleartext passwords, device configurations, and device API keys for firewalls running PAN-OS software.
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 confidenceOS command injection vulnerability in Palo Alto Networks Expedition allows unauthenticated attackers to execute arbitrary OS commands as the www-data user, enabling disclosure of usernames, cleartext passwords, device configurations, and device API keys for firewalls running PAN-OS software.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Expedition versionLocate the installed Palo Alto Networks Expedition version by checking the application interface, management console, or version file typically found in the Expedition installation directoryAffected if The installed version is lower than 1.2.101
-
Verify Expedition network exposureDetermine if the Expedition web interface is accessible from untrusted networks or the public internet by reviewing firewall rules, NAT configurations, or reverse proxy settings that expose the Expedition serviceAffected if Expedition is reachable from untrusted network segments or the internet without proper access controls
-
Review authentication logs for exploitation attemptsExamine Expedition authentication and access logs for failed login attempts, unexpected commands, or activity from unfamiliar IP addresses that may indicate exploitation probingAffected if Logs show repeated unauthenticated requests, unexpected command invocations, or suspicious source IPs targeting the Expedition interface
-
Check for credential exposureInspect the Expedition configuration database and memory for cleartext credentials, API keys, or device configurations that may have been accessed through the vulnerabilityAffected if Credentials, API keys, or firewall configurations stored within or accessible by Expedition appear to have been retrieved or disclosed without authorization
A system is affected if Palo Alto Networks Expedition version is below 1.2.101 and the service is accessible to unauthenticated attackers.
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 vendor-supplied patch immediately; reset all exposed credentials, passwords, and API keys; conduct forensic investigation to determine if exploitation occurred.
Expedition 1.2.101 or later
- 1. Back up your current Expedition configuration and database before upgrading.
- 2. Download the Expedition version 1.2.101 or later from the Palo Alto Networks Customer Support Portal.
- 3. Access the Expedition management interface and navigate to the system upgrade section.
- 4. Upload and apply the Expedition 1.2.101 upgrade package.
- 5. Verify the upgrade was successful by checking the Expedition version in the system information page.
- 6. After upgrade, validate that all expected functionality works correctly, including migration tasks and API key retrieval.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing4.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 $6,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0107 — 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-0107 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