Security readout for executives and security teams
Plain-English summary
phpfm can reportedly let an internet attacker take control of a server without credentials. Default settings leave authentication empty and permit PHP uploads, enabling server-side code execution. A successful attack could expose data, alter content, disrupt service, or provide a foothold into connected systems.
Executive priority
Treat exposed installations as an immediate remediation priority. Isolate or disable them until authentication, upload restrictions, and execution controls are verified. Internally restricted deployments remain serious but can follow after public exposure is contained. Consider incident investigation if suspicious uploads or unexpected PHP files are found.
Technical view
CVE-2026-72592 is a CWE-434 unrestricted file-upload vulnerability reportedly affecting dulldusk phpfm through 1.8.0. The supplied description identifies an empty upload-extension filter and empty default authentication password. This combination permits unauthenticated PHP upload and subsequent server-side execution. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, and no user interaction.
Likely exposure
Highest risk exists where phpfm is deployed on a web-accessible server with default or equivalent settings. Exposure depends on actual deployments, authentication configuration, upload restrictions, and web-server execution permissions. The supplied affected-version metadata is inconsistent, so inventory findings require confirmation against vendor information.
Exploitation context
The supplied bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. Exploitation is nevertheless described as straightforward because it requires network access but no credentials or user interaction. Public exploit availability is not established by the supplied sources.
Researcher notes
The core claim is grounded in the CVE description and referenced source file, but the supplied affected record lists version "0" with unknown default status while the narrative says through 1.8.0. No vendor security advisory, fixed version, patch, or exploitation evidence is included. Validate code state and deployment configuration without testing arbitrary code execution.
Mitigation direction
- Identify and isolate internet-accessible phpfm deployments immediately.
- Disable phpfm where it is unnecessary or cannot be safely restricted.
- Require authentication and restrict access through network controls.
- Block PHP and other executable uploads using an explicit allowlist.
- Prevent uploaded files from executing through web-server configuration.
- Check vendor guidance for a confirmed fixed release or additional mitigation.
Validation and detection
- Inventory servers, containers, images, and web roots for phpfm installations.
- Confirm deployed versions and reconcile them with current vendor guidance.
- Review whether authentication is enabled and protected by a strong secret.
- Inspect upload configuration for an explicit, restrictive extension allowlist.
- Verify uploaded content cannot execute as server-side code.
- Review access, upload, and web-server logs for suspicious activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-72592 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TuranSecVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineTuranSec
CVE Reserved
- Source timelineTuranSec
Public Disclosure
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ProductCVE reference, TuranSec · third-party-advisory
- Vulnerable FileCVE reference, TuranSec · technical-description
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.