How severe is GHSA-jm9x-rx9x-wpqj?

GHSA-jm9x-rx9x-wpqj has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jm9x-rx9x-wpqj?

GHSA-jm9x-rx9x-wpqj affects the following packages: pgadmin4 (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jm9x-rx9x-wpqj?

Update pgadmin4 to version 8.12 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-jm9x-rx9x-wpqj actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-jm9x-rx9x-wpqj, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-jm9x-rx9x-wpqj?

GHSA-jm9x-rx9x-wpqj has an EPSS (Exploit Prediction Scoring System) score of 92.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-jm9x-rx9x-wpqj?

GHSA-jm9x-rx9x-wpqj is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-jm9x-rx9x-wpqj?

A Nuclei detection template exists for GHSA-jm9x-rx9x-wpqj, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-jm9x-rx9x-wpqj published, and has it been updated?

GHSA-jm9x-rx9x-wpqj was published on September 23, 2024 and was last updated on October 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-jm9x-rx9x-wpqj

HIGH

OAuth2 client ID and secret exposed through the web browser

Also known asCVE-2024-9014

Published

Sep 23, 2024

Updated

Oct 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

92.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍pgadmin4

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pgadmin4`	all versions	8.12

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in O…

github.comGithubSep 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-jm9x-rx9x-wpqj in your stack?

O3 detects GHSA-jm9x-rx9x-wpqj across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works