CVE-2024-34067

Workarounds

No workaround is available other than updating to the latest version of the panel.

Importing a malicious egg or gaining access to wings instance could lead to XSS on the panel, which could be used to gain an administrator account on the panel. Specifically, the following things are impacted:

• Egg Docker images
• Egg variables:
  • Name
  • Environment variable
  • Default value
  • Description
  • Validation rules

Additionally, certain fields would reflect malicious input, but it would require the user knowingly entering such input to have an impact.

To iterate, this would require an administrator to perform actions and can't be triggered by a normal panel user.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-34067 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.6); upgrading removes the vulnerable code path.

Kodem intelligence

All of the following commits are required to resolve this security issue:

https://github.com/pterodactyl/panel/commit/1172d71d31561c4e465dabdf6b838e64de48ad16
https://github.com/pterodactyl/panel/commit/f671046947e4695b5e1c647df79305c1cefdf817
https://github.com/pterodactyl/panel/commit/0dad4c5a488661f9adc27dd311542516d9bfa0f2

1. What is CVE-2024-34067? CVE-2024-34067 is a medium-severity cross-site scripting (XSS) vulnerability in pterodactyl/panel (composer), affecting versions < 1.11.6. It is fixed in 1.11.6. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-34067? CVE-2024-34067 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of pterodactyl/panel are affected by CVE-2024-34067? pterodactyl/panel (composer) versions < 1.11.6 is affected.
4. Is there a fix for CVE-2024-34067? Yes. CVE-2024-34067 is fixed in 1.11.6. Upgrade to this version or later.
5. Is CVE-2024-34067 exploitable, and should I be worried? Whether CVE-2024-34067 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-34067 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-34067? Upgrade pterodactyl/panel to 1.11.6 or later.