# CVE-2021-41176: logout CSRF in Pterodactyl Panel

> Attackers can force logged-in users to sign out via CSRF, causing session disruption in Pterodactyl Panel.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m49f-hcxp-6hm6

## What is CVE-2021-41176?

CVE-2021-41176 is a medium-severity vulnerability in pterodactyl panel, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Pterodactyl is an open-source game server management panel built with PHP 7, React, and Go. In affected versions of Pterodactyl a malicious user can trigger a user logout if a signed in user visits a malicious website that makes a request to the Panel's sign-out endpoint. This requires a targeted attack against a specific Panel instance, and serves only to sign a user out. **No user details are leaked, nor is any user data affected, this is simply an annoyance at worst.** This is fixed in version 1.6.3.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-41176?

2 open source packages ship an affected version, including pterodactyl/panel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pterodactyl/panel` | Packagist | From 1.0.0 | 1.6.3 |
| `pterodactyl/panel` | Packagist | From 1.0.0 | 1.6.3 |

Products: Pterodactyl Panel.

## How do I fix CVE-2021-41176?

Upgrade pterodactyl/panel to 1.6.3 or later.

## Is CVE-2021-41176 being exploited?

There is no known exploitation of CVE-2021-41176 in the wild and no public exploit code.

## Other vulnerabilities in pterodactyl panel

- [CVE-2026-26016](https://insights.sbomify.com/CVE-2026-26016/): Pterodactyl Panel Allows Cross-Node Server Configuration Disclosure via Remote API Missing Authorization (critical 9.2)
- [CVE-2021-41129](https://insights.sbomify.com/CVE-2021-41129/): Authentication bypass in Pterodactyl (high 8.1)
- [CVE-2025-68954](https://insights.sbomify.com/CVE-2025-68954/): Pterodactyl does not revoke SFTP access when server is deleted or permissions reduced (high 7.5)
- [CVE-2019-1020002](https://insights.sbomify.com/CVE-2019-1020002/): Pterodactyl vulnerable to 2FA Sniffing (high 7.5)
- [CVE-2025-69197](https://insights.sbomify.com/CVE-2025-69197/): Pterodactyl TOTPs can be reused during validity window (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41176 and fix it if it is affected.

What it is: CVE-2021-41176 is a medium-severity vulnerability in pterodactyl panel, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41176 in the wild and no public exploit code.

Affected packages and fixed versions:
- pterodactyl/panel (Packagist): affected from 1.0.0; fixed in 1.6.3
- pterodactyl/panel (Packagist): affected from 1.0.0; fixed in 1.6.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41176/ (Markdown: https://insights.sbomify.com/CVE-2021-41176/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41176
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41176
- OSV: https://osv.dev/vulnerability/CVE-2021-41176

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41176/
Summaries are generated and may contain mistakes; the official description above is the record.