Skip to main content
mySites.guru
Free Audit
CriticalA PHP security release fixes two CVSS 9.2 flaws, and PHP 8.1 and older get no patchWhat it means for your site
CVE-2026-66492MediumCVSS 6.1CVE published 7 August 2026

Phoca Commander (com_phocacommander) 6.1.2 to 6.1.3 - Authenticated Path Traversal: Arbitrary File Read, Upload, Delete, Copy and Move

Phoca Commander 6.1.2 and 6.1.3 are affected by three path traversal vulnerabilities that the 6.1.2 release did not close. CVE-2026-66491 (CVSS 8.2 High): the getSource function fails to limit paths, allowing any file on the server to be read, including configuration.php and its database credentials. CVE-2026-66492 (CVSS 6.1 Medium): the file upload action does not limit the destination path, so files can be written outside the intended directory. CVE-2026-66493 (CVSS 6.4 Medium): the delete, copy and move actions do not limit paths, so files anywhere on the server can be destroyed or relocated. All three require an authenticated backend user with access to the Phoca Commander file manager (high privileges), but the impact reaches outside the component and outside the site root. Update to 6.1.4 or later, which Phoca released on 5 August 2026 as an explicit security release fixing all three. Note that Joomla will never offer you this update by itself on a Joomla 3, 4 or 5 site: Phoca ships one update manifest whose 6.x entries are pinned to targetplatform 6, so a Joomla 5 site only ever sees the 5.1.0 entry (October 2025, which predates all of these fixes) and reports nothing to do. Install 6.1.4 by hand from https://github.com/PhocaCz/PhocaCommander/releases/download/6.1.4/com_phocacommander_v6.1.4.zip using System, Extensions under Install, then the Install from URL tab. The 6.x builds run fine on Joomla 5. If you cannot update immediately, unpublish or uninstall the Phoca Commander component and restrict backend access to trusted administrators only. Reported by Toan Le.

Is my site affected?

Affected
Phoca Commander from 6.1.2 up to but not including 6.1.4
Fixed in
6.1.4
What to do
Update Phoca Commander to 6.1.4 or later.
Check whether your sites are affected

How CVE-2026-66492 is scored

The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

6.1 Medium

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N

How it is reached

AV:N Attack vector
Network. Reachable across the internet
AC:L Attack complexity
Low. Nothing to work around, it just works
AT:N Attack requirements
None. Works against any affected install
PR:H Privileges required
High. Needs an account with elevated rights
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:N Confidentiality
None. Nothing can be read
VI:N Integrity
None. Nothing can be altered
VA:N Availability
None. The site stays up

What it does beyond the site

SC:N Confidentiality
None. Other systems keep their data
SI:H Integrity
High. Other systems can be altered
SA:N Availability
None. Other systems stay up

Timeline

  1. 7 August 2026CVE-2026-66492 record published by its CNA

Rule details

Other vulnerabilities in Phoca Commander

Updating for CVE-2026-66492 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

Phoca Commander

Latest safe version: 6.1.4

References

CVE-2026-66492 questions

Which versions are affected by CVE-2026-66492?
CVE-2026-66492 affects Phoca Commander from 6.1.2 up to but not including 6.1.4. The fix is in 6.1.4.
How do I fix CVE-2026-66492?
Update Phoca Commander to 6.1.4 or later. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
How severe is CVE-2026-66492?
Joomla CNA scores it 6.1 (Medium) under CVSS 4.0. In plain terms: reachable across the internet, needs an account with elevated rights and nobody has to be tricked into anything.

Running an affected version on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

Rules current as of 24 October 2026.