Affected versions: ≥ 3.0.0 and < 4.2.1
Full advisory: www.php-web-design.com
CVE-2026-103420HighCVSS 7.2CVE published 2 November 2026Added to mySites.guru 3 November 2026
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.
Is my site affected?
CVE-2026-103420 is checked by 4 rules. Find the extension and release line your site runs:
| Extension | Affected versions | Fixed in | What to do |
|---|---|---|---|
| StageIt | from 3.0.0 up to but not including 4.2.1 | 4.2.1 | Update StageIt to 4.2.1 or later. |
| StageIt | from 1.0.0 up to but not including 2.2.1 | 2.2.1 | Update StageIt to 2.2.1 or later. |
| StageIt | from 5.0.0 up to but not including 5.8.0 | 5.8.0 | Update StageIt to 5.8.0 or later. |
| StageIt | from 6.0.0 up to but not including 6.4.0 | 6.4.0 | Update StageIt to 6.4.0 or later. |
How CVE-2026-103420 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.
7.2 High
CVSS 4.0, scored by Joomla CNACVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NHow 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:N Privileges required
- None. No account needed
- UI:P User interaction
- Passive. Someone has to visit a page
What it does to the site
- VC:N Confidentiality
- None. Nothing can be read
- VI:H Integrity
- High. Data and files can be altered at will
- VA:H Availability
- High. The site can be taken down
What it does beyond the site
- SC:N Confidentiality
- None. Other systems keep their data
- SI:N Integrity
- None. Other systems keep their integrity
- SA:N Availability
- None. Other systems stay up
Timeline
- 24 October 2026mySites.guru check added for StageIt (from 5.0.0 up to but not including 5.8.0)
- 24 October 2026mySites.guru check added for StageIt (from 6.0.0 up to but not including 6.4.0)
- 26 October 2026We published: StageIt 5.8.0 and 6.4.0 fix CSRF on every action, and a settings file that could run PHP
- 2 November 2026CVE-2026-103420 record published by its CNA
- 2 November 2026mySites.guru check added for StageIt (from 1.0.0 up to but not including 2.2.1)
- 3 November 2026mySites.guru check added for StageIt (from 3.0.0 up to but not including 4.2.1)
Rule details
StageIt - 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 - 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 - 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
Our disclosure post
Other vulnerabilities in StageIt
Updating for CVE-2026-103420 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.
StageIt
Latest safe version: 6.4.0
- CVE-2026-105600 High, from 3.0.0 up to but not including 4.2.1
- CVE-2026-105601 High, from 3.0.0 up to but not including 4.2.1
References
- CVE-2026-103420 on cve.org (the official CVE record)
- CVE-2026-103420 in the NIST National Vulnerability Database
- php-web-design.com/Information/stageit-4-3-changelog.html
- StageIt 5.8.0 and 6.4.0 fix CSRF on every action, and a settings file that could run PHP
CVE-2026-103420 questions
Which versions are affected by CVE-2026-103420?
CVE-2026-103420 is covered by 4 rules: StageIt from 3.0.0 up to but not including 4.2.1; StageIt from 1.0.0 up to but not including 2.2.1; StageIt from 5.0.0 up to but not including 5.8.0; StageIt from 6.0.0 up to but not including 6.4.0.
How do I fix CVE-2026-103420?
It depends on the extension and release line your site runs. For StageIt from 3.0.0 up to but not including 4.2.1: update StageIt to 4.2.1 or later. For StageIt from 1.0.0 up to but not including 2.2.1: update StageIt to 2.2.1 or later. For StageIt from 5.0.0 up to but not including 5.8.0: update StageIt to 5.8.0 or later. For StageIt from 6.0.0 up to but not including 6.4.0: update StageIt to 6.4.0 or later.
How severe is CVE-2026-103420?
Joomla CNA scores it 7.2 (High) under CVSS 4.0. In plain terms: reachable across the internet, no account needed and someone has to visit a page.
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 15 November 2026.