CVE-2021-41273

Workarounds

Users may optionally manually apply the fixes released in v1.6.6 to patch their own systems.

Due to improperly configured CSRF protections on two routes, a malicious user could execute a CSRF-based attack against the following endpoints:

• Sending a test email.
• Generating a node auto-deployment token.

At no point would any data be exposed to the malicious user, this would simply trigger email spam to an administrative user, or generate a single auto-deployment token unexpectedly. This token is not revealed to the malicious user, it is simply created unexpectedly in the system.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2021-41273 has a CVSS score of 4.3 (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.6.6); upgrading removes the vulnerable code path.

Kodem intelligence

This has been addressed in https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5 which will be released as 1.6.6.

1. What is CVE-2021-41273? CVE-2021-41273 is a medium-severity cross-site request forgery (CSRF) vulnerability in pterodactyl/panel (composer), affecting versions < 1.6.6. It is fixed in 1.6.6. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2021-41273? CVE-2021-41273 has a CVSS score of 4.3 (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-2021-41273? pterodactyl/panel (composer) versions < 1.6.6 is affected.
4. Is there a fix for CVE-2021-41273? Yes. CVE-2021-41273 is fixed in 1.6.6. Upgrade to this version or later.
5. Is CVE-2021-41273 exploitable, and should I be worried? Whether CVE-2021-41273 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-2021-41273 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-2021-41273? Upgrade pterodactyl/panel to 1.6.6 or later.