CVE-2024-9014 — pgadmin4
CRITICALCVE-2024-9014 is a critical-severity (CVSS 9.9) CWE-522 vulnerability in pgadmin4. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for pgadmin4 — see the affected versions and patch details below.
OAuth2 client id and secret exposed through the web browser in pgAdmin 4
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-9014.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
pgadmin4Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pgadmin4 | all versions | 8.12pip install --upgrade 'pgadmin4==8.12' |
Affected Products
pgadmin 4pgadminResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pgadmin4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pgadmin4 to 8.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9014 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How to detect CVE-2024-9014
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-9014 -u https://target- Template
- pgAdmin 4 - Authentication Bypass
- Severity
- critical
- Impact
- Attackers can potentially obtain OAuth2 client ID and secret from exposed configuration in the login page, leading to unauthorized access to user data, authentication bypass, and compromise of pgAdmin 4 instances.
- Remediation
- Update pgAdmin 4 to a version later than 8.11 that addresses the OAuth2 authentication vulnerability and properly secures client credentials from public exposure.
Template by ProjectDiscovery nuclei-templates (s4e-io), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-9014 in your dependencies?
Find it across PyPI, including transitive dependencies.