Skip to main content
mySites.guru
NewAdd every Joomla and WordPress site on a WHM or cPanel server in one goSee how it works
CVE-2026-103419HighCVSS 8.6CVE published 2 November 2026Added to mySites.guru 29 October 2026

Helix Ultimate Framework (helixultimate) 2.2.10 - Authenticated Stored XSS and Hardening Fixes

JoomShaper released Helix Ultimate 2.2.11 on 29 October 2026 as a security update, grading it Moderate (CVSS about 6.5) and stating 2.0.0 to 2.2.10 are affected. Versions below 2.2.10 are already covered by the earlier Helix Ultimate rules; this row covers 2.2.10. The most significant fix: the 2.2.10 blog audio/video embed sanitiser (Helper::sanitizeEmbed) passed its allowed iframe/audio/video tag and attribute lists to Joomla InputFilter in blacklist mode, so the list meant to be the only tags allowed was the list removed, weakening the 2.2.10 stored XSS fix for embed inputs. 2.2.11 switches it to a strict allow-list. Also fixed: escaping of file and folder names, paths and breadcrumbs in the framework media picker (XSS), regex validation of the error page preset name (path traversal in a stylesheet path), Mega Menu badge sanitisation, and a tighter check that Blog image removal only touches images the article actually references. Every fix requires a logged-in user with edit rights; nothing unauthenticated. Published as CVE-2026-105602 (Mega Menu badge text stored XSS) and CVE-2026-103419 (media picker stored XSS) on 2 Nov 2026, both CVSS 4.0 8.6 High. Update the System - Helix Ultimate Framework plugin to 2.2.11 or later. The Helix Ultimate TEMPLATE (shaper_helixultimate) is a separate install with its own entry in Joomla Updates, and must be updated as well.

Is my site affected?

CVE-2026-103419 is checked by 2 rules. Find the extension and release line your site runs:

ExtensionAffected versionsFixed inWhat to do
Helix Ultimate Frameworkfrom 2.2.10 up to but not including 2.2.112.2.11Update Helix Ultimate Framework to 2.2.11 or later.
Helix Ultimatefrom 2.2.10 up to but not including 2.2.112.2.11Update Helix Ultimate to 2.2.11 or later.

How CVE-2026-103419 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.

8.6 High

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/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:L Privileges required
Low. Any logged-in account will do
UI:P User interaction
Passive. Someone has to visit a page

What it does to the site

VC:H Confidentiality
High. Everything the site holds can be read
VI:H Integrity
High. Data and files can be altered at will
VA:L Availability
Low. The site slows or stutters

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

  1. 29 October 2026mySites.guru check added for Helix Ultimate Framework (from 2.2.10 up to but not including 2.2.11)
  2. 29 October 2026mySites.guru check added for Helix Ultimate (from 2.2.10 up to but not including 2.2.11)
  3. 29 October 2026We published: Helix Ultimate 2.2.11 Is a Security Release. Now Its Download Page Says So.
  4. 2 November 2026CVE-2026-103419 record published by its CNA

Rule details

Helix Ultimate - Helix Ultimate (shaper_helixultimate) 2.2.10 - Authenticated Stored XSS and Hardening Fixes

JoomShaper released Helix Ultimate 2.2.11 on 29 October 2026 as a security update, grading it Moderate (CVSS about 6.5) and stating 2.0.0 to 2.2.10 are affected. THIS ROW IS THE TEMPLATE (shaper_helixultimate), which is installed separately from the System - Helix Ultimate Framework plugin and is listed as its own update in Joomla Updates (System, Update, Extensions) - updating the plugin alone does not clear it. Template-side fixes in 2.2.11: the error page now validates the preset stylesheet name against /^[A-Za-z0-9_-]+$/ (path traversal into the stylesheet path), and article rating now checks the rating is 1 to 5 and the article is published. The framework plugin half of this release fixes the embed sanitiser that ran in blacklist mode in 2.2.10, media picker escaping and Mega Menu badge sanitisation. Every fix requires a logged-in user with edit rights; nothing unauthenticated. Published as CVE-2026-105602 (Mega Menu badge text stored XSS) and CVE-2026-103419 (media picker stored XSS) on 2 Nov 2026, both CVSS 4.0 8.6 High. Update the template to 2.2.11 through Joomla Updates, or install the 2.2.11 Template package from JoomShaper.

Affected versions: ≥ 2.2.10 and < 2.2.11

Full advisory: our disclosure post

Our disclosure post

Other vulnerabilities in Helix Ultimate Framework and Helix Ultimate

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

Helix Ultimate Framework

Latest safe version: 2.2.11

Helix Ultimate

Latest safe version: 2.2.11

References

CVE-2026-103419 questions

Which versions are affected by CVE-2026-103419?
CVE-2026-103419 is covered by 2 rules: Helix Ultimate Framework from 2.2.10 up to but not including 2.2.11; Helix Ultimate from 2.2.10 up to but not including 2.2.11.
How do I fix CVE-2026-103419?
It depends on the extension and release line your site runs. For Helix Ultimate Framework from 2.2.10 up to but not including 2.2.11: update Helix Ultimate Framework to 2.2.11 or later. For Helix Ultimate from 2.2.10 up to but not including 2.2.11: update Helix Ultimate to 2.2.11 or later.
How severe is CVE-2026-103419?
Joomla CNA scores it 8.6 (High) under CVSS 4.0. In plain terms: reachable across the internet, any logged-in account will do 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 14 November 2026.