How severe is GHSA-fg52-xjfc-9rh8?

GHSA-fg52-xjfc-9rh8 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fg52-xjfc-9rh8?

GHSA-fg52-xjfc-9rh8 affects the following packages: pterodactyl/panel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-fg52-xjfc-9rh8?

Update pterodactyl/panel to 0.7.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fg52-xjfc-9rh8 is resolved across your whole dependency graph.

How do I detect GHSA-fg52-xjfc-9rh8 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pterodactyl/panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fg52-xjfc-9rh8 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-fg52-xjfc-9rh8?

O3 pinpoints whether GHSA-fg52-xjfc-9rh8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fg52-xjfc-9rh8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fg52-xjfc-9rh8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fg52-xjfc-9rh8?

GHSA-fg52-xjfc-9rh8 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 70th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fg52-xjfc-9rh8?

GHSA-fg52-xjfc-9rh8 is classified as CWE-203 (CWE-203). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fg52-xjfc-9rh8 published, and has it been updated?

GHSA-fg52-xjfc-9rh8 was published on May 24, 2022 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-fg52-xjfc-9rh8

HIGH

Pterodactyl vulnerable to 2FA Sniffing

Also known asCVE-2019-1020002

Published

May 24, 2022

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk70th percentile+1.08%

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

🐘pterodactyl/panel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Pterodactyl version 0.7.13 and lower - 2FA Sniffing

Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.

Impact

Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.

A logical mistake was made when the original code was written that would wait to verify the user's password until they had provided 2FA credentials if it was enabled on their account. However, because of this you could enter a bad password for a known email and determine if the account exists if you got redirected to a 2FA page.

For more information

If you have any questions or comments about this advisory please react out on Discord or email dane@[project name].io.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pterodactyl/panel`	all versions	0.7.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pterodactyl/panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update pterodactyl/panel to 0.7.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fg52-xjfc-9rh8 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 O3 protects you
O3 pinpoints whether GHSA-fg52-xjfc-9rh8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fg52-xjfc-9rh8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Pterodactyl version 0.7.13 and lower - 2FA Sniffing** Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields. ### Impact Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields. A logical mistake was made when the original code was written that would wait to verify the user's password until they had provided 2FA credentials if it was

O3 Security · Impact-Aware SCA

Is GHSA-fg52-xjfc-9rh8 in your dependencies?

O3 detects GHSA-fg52-xjfc-9rh8 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works