dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-54473

CRITICAL · 9.2 CVSS v4.0 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authenticated RCE vulnerability in Phoca Commander component 1.0.0-4.0.0 and 5.0.0-5.0.1 for Joomla was discovered. The issue allows code execution via the unzip feature.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated remote code execution vulnerability in Phoca Commander component for Joomla versions 1.0.0-4.0.0 and 5.0.0-5.0.1. The unzip feature allows authenticated users to execute arbitrary code on the underlying server, granting full control over the affected system.

MitigationRestrict administrative access to the Phoca Commander component to trusted users only; monitor for unauthorized access; apply vendor patch when available; consider disabling or removing the unzip functionality if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
None
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:X/V:X/RE:L/U:Clear

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Phoca Commander is installed
    Log into the Joomla Administrator backend and navigate to Components > Manage > Extensions. Search for 'Phoca Commander' in the installed components list. Alternatively, check for the component directory at /administrator/components/com_phocacommander/ or /components/com_phocacommander/ on the server filesystem.
    Affected if Phoca Commander component appears in the extensions list or component directories exist on the server.
  2. Determine the installed Phoca Commander version
    In the Joomla Administrator panel, go to Components > Phoca Commander. Look for a version number typically displayed in the component header, about page, or help menu. If accessing the filesystem, check for a version.xml or manifest file within the component directory that lists the installed version.
    Affected if The installed version number falls within 1.0.0 through 4.0.0 OR 5.0.0 through 5.0.1.
  3. Confirm the unzip feature is accessible
    In the Joomla Administrator panel, navigate to Components > Phoca Commander and locate the unzip or extraction feature within the file management interface. Verify whether this feature is enabled and visible to authenticated users.
    Affected if The unzip/extraction functionality is present and accessible to authenticated users in the Phoca Commander interface.
  4. Verify user access to the component
    In Joomla Administrator, go to Users > Groups or Users > Access Levels to review which user groups have permission to access the Phoca Commander component. Check the component's configuration under Options > Permissions to identify which user roles can use the unzip feature.
    Affected if Any user group beyond a single trusted administrator has access to the Phoca Commander component and its unzip functionality.

The environment is affected if Phoca Commander is installed with a version between 1.0.0-4.0.0 or 5.0.0-5.0.1, the unzip feature is accessible, and users beyond a single trusted administrator have access to the component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict administrative access to the Phoca Commander component to trusted users only; monitor for unauthorized access; apply vendor patch when available; consider disabling or removing the unzip functionality if not required.

Recommended fix Moderate confidence

Phoca Commander 5.0.2 or later (or version 4.0.1 if remaining on the 4.x branch)

  1. 1. Verify the currently installed Phoca Commander version in Joomla admin panel under Components > Phoca Commander
  2. 2. If running version 1.0.0-4.0.0 or 5.0.0-5.0.1, backup the Joomla site and database before proceeding
  3. 3. Download the latest version of Phoca Commander from the official source at phoca.cz
  4. 4. Install the updated version through Joomla's extension manager (Extensions > Manage > Install)
  5. 5. Clear any caching mechanisms after upgrade
  6. 6. Verify the unzip functionality works correctly with test archives
  7. 7. Confirm the component version reflects the updated release in Joomla admin
Caveat Review changelog at phoca.cz for any breaking changes between 5.0.1 and the target version before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54473 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data