How severe is GHSA-mgr9-6c2j-jxrq?

No CVSS score has been assigned to GHSA-mgr9-6c2j-jxrq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mgr9-6c2j-jxrq?

GHSA-mgr9-6c2j-jxrq affects the following packages: pterodactyl/panel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mgr9-6c2j-jxrq?

Update pterodactyl/panel to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgr9-6c2j-jxrq is resolved across your whole dependency graph.

How do I detect GHSA-mgr9-6c2j-jxrq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pterodactyl/panel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mgr9-6c2j-jxrq 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-mgr9-6c2j-jxrq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mgr9-6c2j-jxrq can be triaged on real exposure rather than presence alone.

Is GHSA-mgr9-6c2j-jxrq actively exploited in the wild?

No public exploit code has been indexed for GHSA-mgr9-6c2j-jxrq 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.

When was GHSA-mgr9-6c2j-jxrq published, and has it been updated?

GHSA-mgr9-6c2j-jxrq was published on December 30, 2025 and was last updated on December 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-mgr9-6c2j-jxrq — pterodactyl/panel

Fix: pterodactyl/panel@1570ff2

GHSA-mgr9-6c2j-jxrq is a security vulnerability in pterodactyl/panel. A fix is available for pterodactyl/panel — see the affected versions and patch details below.

Pterodactyl has a Reflected XSS vulnerability in “Create New Database Host”

Published

Dec 30, 2025

Updated

Dec 30, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 30, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

[!NOTE] Message from the Pterodactyl team:

The Pterodactyl team has evaluated this as a minor security issue but does not consider it something that should be assigned a CVE, nor does it require active patching by vulnerable systems.

This issue is entirely self-inflicted and requires an administrative user paste an obviously incorrect value into a database host field, submit it, and run into the XSS when the error message is rendered. However, we have determined that this fix is good security hygiene and may prevent issues in other areas not yet discovered.

Summary

When an administrative user creates a new database host they are prompted to provide a Host value which is expected to be a domain or IP address. When an invalid value is encountered and passed back to gethostaddr and/or directly to the MySQL connection tooling, an error is returned. This error is then passed back along to the front-end, but was not properly sanitized when rendered.

Therefore it is possible for an admin to knowingly paste a malicious payload such as <script>prompt(document.domain)</script> into the Host field and XSS themselves.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pterodactyl/panel`	all versions	1.12.0`composer require pterodactyl/panel:^1.12.0`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pterodactyl/panel to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgr9-6c2j-jxrq 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mgr9-6c2j-jxrq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mgr9-6c2j-jxrq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

> [!NOTE] > Message from the Pterodactyl team: > > The Pterodactyl team has evaluated this as a minor security issue but does not consider it something that should be assigned a CVE, nor does it require active patching by vulnerable systems. > > This issue is entirely self-inflicted and requires an administrative user paste an _obviously_ incorrect value into a database host field, submit it, and run into the XSS when the error message is rendered. However, we have determined that this fix is good security hygiene and may prevent issues in other areas not yet discovered. ### Summary When an a

O3 Security · Impact-Aware SCA

Is GHSA-mgr9-6c2j-jxrq in your dependencies?

O3 Security finds GHSA-mgr9-6c2j-jxrq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works