# CVE-2024-5910: Palo Alto Networks Expedition Missing Authentication

> Attackers with network access can take over admin accounts and access sensitive configuration data due to missing authentication in Palo Alto Expedition.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/AU:Y/R:U/V:D/RE:M/U:Red`)
- **Exploited in the wild:** Yes, since 7 Nov 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-px3f-fc5j-2fqv

## What is CVE-2024-5910?

CVE-2024-5910 is a critical missing authorization vulnerability in Palo Alto Networks Expedition, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authentication for a critical function in Palo Alto Networks Expedition can lead to an Expedition admin account takeover for attackers with network access to Expedition.

Note: Expedition is a tool aiding in configuration migration, tuning, and enrichment. Configuration secrets, credentials, and other data imported into Expedition is at risk due to this issue.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-5910?

It affects 1 product.


Products: Paloaltonetworks Expedition.

## How do I fix CVE-2024-5910?

No fix has been published for CVE-2024-5910 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Nov 2024.

## Is CVE-2024-5910 being exploited?

Yes. Attackers have exploited CVE-2024-5910 in the wild since at least 7 Nov 2024.

Public exploit code:

- Palo Alto Expedition Remote Code Execution (CVE-2024-5910 and CVE-2024-9464) (metasploit)
- Palo Alto Networks Expedition 1.2.90.1 - Admin Account Takeover (exploitdb)
- Palo Alto Expedition - Admin Account Takeover (nuclei): http/cves/2024/CVE-2024-5910.yaml

## Other vulnerabilities in Palo Alto Networks Expedition

- [CVE-2024-9463](https://insights.sbomify.com/CVE-2024-9463/): Palo Alto Networks Expedition OS Command Injection (critical 9.9, exploited in the wild)
- [CVE-2024-9465](https://insights.sbomify.com/CVE-2024-9465/): Palo Alto Networks Expedition SQL Injection (critical 9.2, exploited in the wild)
- [CVE-2018-10143](https://insights.sbomify.com/CVE-2018-10143/): Command injection in Palo Alto Networks Expedition (critical 9.8)
- [CVE-2024-9464](https://insights.sbomify.com/CVE-2024-9464/): Expedition: Authenticated OS Command Injection Vulnerability Leads to Firewall Admin Credential Disclosure (critical 9.3)
- [CVE-2025-0103](https://insights.sbomify.com/CVE-2025-0103/): Expedition: SQL Injection Vulnerability (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5910 and fix it if it is affected.

What it is: CVE-2024-5910 is a critical missing authorization vulnerability in Palo Alto Networks Expedition, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-5910 in the wild since at least 7 Nov 2024.

Affected product: Palo Alto Networks Expedition. 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-2024-5910/ (Markdown: https://insights.sbomify.com/CVE-2024-5910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5910
- OSV: https://osv.dev/vulnerability/CVE-2024-5910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5910/
Summaries are generated and may contain mistakes; the official description above is the record.