cve.bz

CVE-2023-25168 pterodactyl wings: Link Following

8.2 highEPSS 1.0%Fix available

High (8.2) in pterodactyl wings. EPSS 1.0% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/pterodactyl/wings 1.11.4, 1.7.4.

On this page
Wings is Pterodactyl's server control plane. This vulnerability can be used to delete files and directories recursively on the host system. This vulnerability can be combined with `GHSA-p8r3-83r8-jwj5` to overwrite files on the host system. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by Wings. This vulnerability has been resolved in version `v1.11.4` of Wings, and has been back-ported to the 1.7 release series in `v1.7.4`. Anyone running `v1.11.x` should upgrade to `v1.11.4` and anyone running `v1.7.x` should upgrade to `v1.7.4`. There are no known workarounds for this issue.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd 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: no · Technical impact: partial, assessed 2025-03-10. 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-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-25168 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-25168?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-25168?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-2023-25168 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 NVD's CPE matches.

ProductAffected
pterodactyl:wingsfrom 1.7.0 before 1.7.4
pterodactyl:wings1.11.0
pterodactyl:wings1.11.1
pterodactyl:wings1.11.2
pterodactyl:wings1.11.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-66p8-j459-rq63Gogithub.com/pterodactyl/wings<1.7.41.7.4
GHSA-66p8-j459-rq63Gogithub.com/pterodactyl/wings>=1.11.0 <1.11.41.11.4
GO-2023-1555Gogithub.com/pterodactyl/wings<1.7.4
>=1.11.0 <1.11.4
1.7.4, 1.11.4

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

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

References

Check your stackJSON