Skip to main content
mySites.guru
Free Audit
CriticalPHP2Shell is fixed, but a researcher now claims six more unpatched PHP flaws. Nothing to do today, but PHP is not out of the woodsWhat to prepare

Cotton Cloud security vulnerabilities

mySites.guru tracks 2 vulnerabilities in Cotton Cloud (com_cotton), covering 2 CVEs. Every connected Joomla site is checked against them on each audit.

Is my site affected?

Your site is affected if it runs Cotton Cloud in any of these ranges:

  • from 2.0.2 up to but not including 2.0.3
  • before 2.0.2
Latest safe version
2.0.3 or later. No rule we check matches that release or any newer one.
What to do
Update Cotton Cloud to 2.0.3 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
Check whether your sites are affected

Every Cotton Cloud vulnerability we track

Newest first. CVSS is the score published in each CVE record, where it has one; the severity column is the rating our check uses.

CVEAffected versionsFixed inSeverityAdded
CVE-2026-67283CVSS 6.9before 2.0.22.0.2Unrated-
CVE-2026-67284CVSS 5.3from 2.0.2 up to but not including 2.0.32.0.3Unrated-

What we check for

CVE-2026-67283

Cotton Cloud (com_cotton) below 2.0.2 - Unauthenticated Access to the Entire File Store (CVE-2026-67283)

Cotton Cloud is a database backed cloud file store for Joomla, shipped as the pkg_cotton package (com_cotton file manager, com_shuttle terminal and MCP server, com_weaver editor, mod_cotton, plg_editors-xtd_cotton, LibCotton). In every release up to and including 2.0.1 the login check sits in the view layer, so it only runs when the component renders a page. The task endpoints never construct the view, and their only gate is a CSRF token check, which Joomla happily issues to an anonymous visitor. A visitor with no account and no session can therefore read, overwrite, delete and re-assign permissions on every file held in the store, regardless of who owns it, and can create new files inside another user's folder. Because the component serves stored files with a Content-Type derived from the file extension, an uploaded .html file is returned as text/html and executes on the site's own origin, which makes stored cross site scripting a downstream consequence. This is not remote code execution: files live in a database column, never on a web served path, so a stored .php file is echoed as bytes rather than executed. CVE-2026-67283, CVSS 4.0 6.9 Medium (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N), CWE-284 improper access control, published 12 August 2026 by the Joomla CNA and reported by Phil Taylor of mySites.guru. Update to Cotton Cloud 2.0.2 or later. Interim mitigation: unpublish any Cotton menu items and unpublish the Cotton and Shuttle components, since unpublishing the menu item alone does not close the task endpoints.

Affected versions: < 2.0.2

Full advisory: www.cve.org

CVE-2026-67284

Cotton Cloud (com_cotton) 2.0.2 - Authenticated Access to Every Other User's Files (CVE-2026-67284)

Cotton Cloud 2.0.2 fixed the unauthenticated access covered by CVE-2026-67283 but left the underlying authorisation flaw in place. The by-id database accessors fetch files and folders by their numeric id with no check that the id belongs to the caller, so any authenticated user can read, overwrite, delete and re-assign permissions on files owned by any other user. On a site with open user registration, which is the normal setup for a file store, a free account is enough. The component also sets the response content type from the file extension, so an attacker can plant an HTML file that serves script from the site's own origin. CVSS 4.0 5.3 MEDIUM (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N), CWE-284. Update to Cotton Cloud 2.0.3 or later. Reported by Phil Taylor of mySites.guru.

Affected versions: ≥ 2.0.2 and < 2.0.3

Full advisory: our disclosure post

Timeline

  1. 12 August 2026CVE-2026-67283 record published
  2. 12 August 2026CVE-2026-67284 record published

References

Each CVE page above links its official cve.org record and its NVD entry.

Cotton Cloud vulnerability questions

Which versions of Cotton Cloud are vulnerable?
mySites.guru tracks 2 vulnerabilities in Cotton Cloud (com_cotton). A site is affected if its installed version is in any of these ranges: from 2.0.2 up to but not including 2.0.3; before 2.0.2.
What is the latest safe version of Cotton Cloud?
2.0.3. Every vulnerability tracked here is fixed by 2.0.3, and no rule we check matches that release or any later one.
How do I check which version of Cotton Cloud my Joomla site runs?
The installed version is listed on the Joomla administrator's Extensions: Manage screen; search it for com_cotton. mySites.guru reads the installed version on every audit of a connected site and checks it against these rules.

Running Cotton Cloud 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.

CVE identifiers: CVE-2026-67283, CVE-2026-67284. Rules current as of 25 October 2026.