Skip to main content
mySites.guru
NewIntroducing Checklists on mySites.guru: create unlimited task lists with automated and manual stepsSee how it works

StageIt security vulnerabilities

mySites.guru tracks 4 vulnerabilities in StageIt (com_stageit), covering 3 CVEs. Every connected Joomla site is checked against them on each audit.

Is my site affected?

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

  • from 6.0.0 up to but not including 6.4.0
  • from 5.0.0 up to but not including 5.8.0
  • from 3.0.0 up to but not including 4.2.1
  • from 1.0.0 up to but not including 2.2.1
Latest safe version
6.4.0 or later. No rule we check matches that release or any newer one.
What to do
Update StageIt to 6.4.0 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

Every StageIt 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-103420CVSS 7.2CVE-2026-105600CVSS 8.6CVE-2026-105601CVSS 5.3from 3.0.0 up to but not including 4.2.14.2.1High2026-11-03
CVE-2026-103420CVSS 7.2CVE-2026-105600CVSS 8.6CVE-2026-105601CVSS 5.3from 1.0.0 up to but not including 2.2.12.2.1High2026-11-02
CVE-2026-103420CVSS 7.2CVE-2026-105600CVSS 8.6CVE-2026-105601CVSS 5.3from 5.0.0 up to but not including 5.8.05.8.0High2026-10-24
CVE-2026-103420CVSS 7.2CVE-2026-105600CVSS 8.6CVE-2026-105601CVSS 5.3from 6.0.0 up to but not including 6.4.06.4.0High2026-10-24

What we check for

StageIt (com_stageit) 2.x below 2.2.1 and 4.x below 4.2.1 - CSRF on every action, PHP Code Injection via Options, Backup Path Traversal and XSS

CVE-2026-103420 (CSRF on every action, CVSS 4.0 7.2 High), CVE-2026-105600 (PHP code injection via settings strings, 8.6 High) and CVE-2026-105601 (reflected XSS, 5.3 Medium) also affect the older StageIt lines for Joomla 3 (2.x) and Joomla 4 (4.x). Before 2.2.1 and 4.2.1 there was no CSRF token check on any action, a setting containing an apostrophe could break out of params.php and run as PHP, backup delete and restore accepted any folder path, and the StageIt bar and tab parameter allowed reflected XSS. The vendor fixed the settings break-out in 2.2.0 and 4.2.0 and the rest in 2.2.1 and 4.2.1, all released on 29 Oct 2026. Update to StageIt 2.2.1 (Joomla 3) or 4.2.1 (Joomla 4) or later. The CVE records still list 1.0 to 5.7.5 as affected; the fixed versions here come from the vendor changelog.

Affected versions: ≥ 3.0.0 and < 4.2.1

Full advisory: www.php-web-design.com

StageIt (com_stageit) 2.x below 2.2.1 and 4.x below 4.2.1 - CSRF on every action, PHP Code Injection via Options, Backup Path Traversal and XSS

CVE-2026-103420 (CSRF on every action, CVSS 4.0 7.2 High), CVE-2026-105600 (PHP code injection via settings strings, 8.6 High) and CVE-2026-105601 (reflected XSS, 5.3 Medium) also affect the older StageIt lines for Joomla 3 (2.x) and Joomla 4 (4.x). Before 2.2.1 and 4.2.1 there was no CSRF token check on any action, a setting containing an apostrophe could break out of params.php and run as PHP, backup delete and restore accepted any folder path, and the StageIt bar and tab parameter allowed reflected XSS. The vendor fixed the settings break-out in 2.2.0 and 4.2.0 and the rest in 2.2.1 and 4.2.1, all released on 29 Oct 2026. Update to StageIt 2.2.1 (Joomla 3) or 4.2.1 (Joomla 4) or later. The CVE records still list 1.0 to 5.7.5 as affected; the fixed versions here come from the vendor changelog.

Affected versions: ≥ 1.0.0 and < 2.2.1

Full advisory: www.php-web-design.com

StageIt (com_stageit) 5.x below 5.8.0 and 6.x below 6.4.0 - CSRF on every action, PHP Code Injection via Options, Backup Path Traversal and XSS

StageIt before 5.8.0 (Joomla 5 line) and before 6.4.0 (Joomla 6 line) had no CSRF token check on any action (build, push, remove, restore and delete backups, save Options, clear logs), so another website could trigger them through a logged-in administrator's browser. A setting containing an apostrophe could break out of the settings file params.php and run as PHP, the backup delete and restore actions accepted any folder path, the StageIt bar links and the tab parameter allowed reflected XSS, and any visitor could switch the StageIt bar off. Fixed in 5.8.0 and 6.4.0 (24 Oct 2026). Published as CVE-2026-103420 (CSRF, CVSS 4.0 7.2 High), CVE-2026-105600 (PHP code injection via settings strings, 8.6 High) and CVE-2026-105601 (reflected XSS, 5.3 Medium) on 2 Nov 2026. The older lines for Joomla 3 and 4 were fixed in StageIt 2.2.1 and 4.2.1 (29 Oct 2026) and are covered by separate rules.

Affected versions: ≥ 5.0.0 and < 5.8.0

Full advisory: our disclosure post

StageIt (com_stageit) 5.x below 5.8.0 and 6.x below 6.4.0 - CSRF on every action, PHP Code Injection via Options, Backup Path Traversal and XSS

StageIt before 5.8.0 (Joomla 5 line) and before 6.4.0 (Joomla 6 line) had no CSRF token check on any action (build, push, remove, restore and delete backups, save Options, clear logs), so another website could trigger them through a logged-in administrator's browser. A setting containing an apostrophe could break out of the settings file params.php and run as PHP, the backup delete and restore actions accepted any folder path, the StageIt bar links and the tab parameter allowed reflected XSS, and any visitor could switch the StageIt bar off. Fixed in 5.8.0 and 6.4.0 (24 Oct 2026). Published as CVE-2026-103420 (CSRF, CVSS 4.0 7.2 High), CVE-2026-105600 (PHP code injection via settings strings, 8.6 High) and CVE-2026-105601 (reflected XSS, 5.3 Medium) on 2 Nov 2026. The older lines for Joomla 3 and 4 were fixed in StageIt 2.2.1 and 4.2.1 (29 Oct 2026) and are covered by separate rules.

Affected versions: ≥ 6.0.0 and < 6.4.0

Full advisory: our disclosure post

Timeline

  1. 24 October 2026Check added for CVE-2026-103420, CVE-2026-105600 and CVE-2026-105601 (from 5.0.0 up to but not including 5.8.0)
  2. 24 October 2026Check added for CVE-2026-103420, CVE-2026-105600 and CVE-2026-105601 (from 6.0.0 up to but not including 6.4.0)
  3. 2 November 2026Check added for CVE-2026-103420, CVE-2026-105600 and CVE-2026-105601 (from 1.0.0 up to but not including 2.2.1)
  4. 2 November 2026CVE-2026-103420 record published
  5. 2 November 2026CVE-2026-105600 record published
  6. 2 November 2026CVE-2026-105601 record published
  7. 3 November 2026Check added for CVE-2026-103420, CVE-2026-105600 and CVE-2026-105601 (from 3.0.0 up to but not including 4.2.1)

References

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

StageIt vulnerability questions

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

Running StageIt 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-103420, CVE-2026-105600, CVE-2026-105601. Rules current as of 17 November 2026.