Affected versions: ≥ 3.0.0 and < 6.1.9
Full advisory: our disclosure post
Phoca Cart before 6.1.9 does not check who is downloading a purchased file. The order download task loads the ordered file by its numeric id and only checks that the download token and order token sent with the request are not empty. It never compares them with the tokens stored for that order. No login is required: an anonymous visitor who sends any non-empty values for both tokens can step through the sequential download ids and fetch the digital products other customers paid for. Only shops that sell downloadable products are exposed, and the per-file download count and day limits still apply. Phoca describes it as an authorisation bypass through a user-controlled key (IDOR) in the order view. Phoca Cart 6.1.9 (1 October 2026) requires the logged-in owner of the order, or both stored tokens matched exactly. The fix has shipped on the 6.x branch only. The current 5.x release (5.2.4), 4.x release (4.0.13) and 3.x release (3.5.8) all have the same unchecked code and no fixed release. Joomla 5 and Joomla 6 sites should install the 6.1.9 package (a Joomla 5 site is offered the 5.x line by the updater, so install pkg_phocacart_v6.1.9.zip by hand). Joomla 3 and Joomla 4 sites have no fix: unpublish downloadable products, or move to Joomla 5 or 6 and Phoca Cart 6.1.9. A CVE has been announced by Phoca but not yet published.
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.
8.7 High
CVSS 4.0, scored by Joomla CNACVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NAffected versions: ≥ 3.0.0 and < 6.1.9
Full advisory: our disclosure post
Updating for CVE-2026-102775 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.
Latest safe version: 6.1.9
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 8 October 2026.