ExpeditionApplication · Paloaltonetworks
CVE-2025-0103
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 SQL injection vulnerability in Palo Alto Networks Expedition enables an authenticated attacker to reveal Expedition database contents, such as password hashes, usernames, device configurations, and device API keys. This vulnerability also enables attackers to create and read arbitrary files on the Expedition system.
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 · moderate confidenceSQL injection vulnerability in Palo Alto Networks Expedition allows authenticated attackers to execute arbitrary SQL queries, exposing sensitive database contents including password hashes, usernames, device configurations, and API keys. The vulnerability also permits arbitrary file creation and reading on the host system.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installation and versionAccess the Expedition web interface and navigate to the About or Settings page to view the installed version number. Alternatively, check system documentation or installation files for version information.Affected if The installed version is below 1.2.101
-
Confirm network exposureReview firewall rules, network configurations, or access control lists to determine if Expedition management interface is accessible from untrusted networks or the internet.Affected if Expedition is reachable from untrusted or public networks without proper access restrictions
-
Review authentication configurationCheck user accounts and authentication settings within Expedition to identify all accounts with access to the SQL injection-vulnerable endpoints.Affected if Multiple or weakly secured accounts exist with access to Expedition admin functions
-
Inspect for suspicious database accessReview Expedition logs, database query logs, or audit trails for unexpected or unauthorized SQL queries, especially those targeting system tables, user credentials, or configuration data.Affected if Logs show SQL queries originating from unexpected sources, unusual query patterns, or access to sensitive tables like user credentials or device configurations
You are affected if Expedition version is below 1.2.101 and the management interface is accessible to untrusted users, regardless of whether exploitation has occurred.
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 patches when released; prior to patch, restrict network access to Expedition to trusted administrators only and monitor for suspicious activity.
Expedition 1.2.101 or later
- Backup all Expedition data and configurations before upgrading
- Download Expedition version 1.2.101 or later from the Palo Alto Networks support portal
- Follow the official Expedition upgrade documentation to apply the update
- After upgrading, verify the Expedition version reflects 1.2.101 or higher
- Confirm the SQL injection vulnerability is no longer present by testing that database queries properly sanitize input
- Review user accounts and rotate any credentials that may have been exposed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0103 — 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-0103 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