cve.bz

CVE-2025-49132 pterodactyl panel: Code Injection

10.0 criticalExploitEPSS 56%Fix available

Critical (10.0) in pterodactyl panel. EPSS 56% estimated probability of exploitation activity in the next 30 days. Fixed in pterodactyl/panel 1.11.11.

On this page
Pterodactyl is a free, open-source game server management panel. Prior to version 1.11.11, using the /locales/locale.json with the locale and namespace query parameters, a malicious actor is able to execute arbitrary code without being authenticated. With the ability to execute arbitrary code it could be used to gain access to the Panel's server, read credentials from the Panel's config, extract sensitive information from the database, access files of servers managed by the panel, etc. This issue has been patched in version 1.11.11. There are no software workarounds for this vulnerability, but use of an external Web Application Firewall (WAF) could help mitigate this attack.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
56% (unchanged from 54% a week ago; 54% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-06-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • pterodactyl/panel (Packagist): fixed in 1.11.11

Ask an AI about this CVE

Show the promptExplain CVE-2025-49132 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-49132?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-49132?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-49132 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
pterodactyl panel< 1.11.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-24wv-6c99-f843Packagistpterodactyl/panel<1.11.111.11.11

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • YoyoChaud/CVE-2025-49132 Harbor Check: matches CVE 25 stars, Python, created
    Exploit for Pterodactyl Panel ≤ 1.11.10 - unauthenticated LFI to RCE.
  • Zen-kun04/CVE-2025-49132 Harbor Check: matches CVE 16 stars, created
    A script that gives you the credentials of a Pterodactyl panel vulnerable to CVE-2025-49132
  • malw0re/CVE-2025-49132-Mods Harbor Check: matches CVE 11 stars, Python, created
  • str1keboo/CVE-2025-49132 Harbor Check: matches CVE 5 stars, Python, created
    This repository contains a Proof of Concept (PoC) for CVE-2025-49132, a critical vulnerability in Pterodactyl Panel versions < 1.11.11.
  • 63square/CVE-2025-49132 Harbor Check: matches CVE 5 stars, created
    PoCs for CVE-2025-49132
20 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON