Skip to main content
mySites.guru
Free Audit
J!Awards 2026mySites.guru is shortlisted for Your Favourite Tool in Your Joomla WorkflowVote by 11 OctoberHow to vote
CVE-2026-102426MediumCVSS 5.3CVE published 5 October 2026Added to mySites.guru 5 October 2026

SP Page Builder (com_sppagebuilder) 5.5.0 to 5.7.x - Unauthenticated Reflected XSS in the Dynamic Content Filter addon

SP Page Builder Pro's Dynamic Content Filter addon takes the range-slider minimum and maximum from the dc_filter_<fieldId> request parameter, escapes the value inside the data-value attribute, and then prints the same value unescaped as the label's text a few characters later. An unauthenticated attacker can send a crafted link to a page using the filter and run script in the browser of whoever opens it, as the site (CVE-2026-102426, CVSS 4.0 5.3 Medium as scored by the Joomla CNA). The CNA record gives the range as 3.0.0 to 5.6.1 with the 1.0.2 Joomla 3 patch applied; this rule starts at 5.5.0 because dynamic content first shipped in 5.5.0 and the 3.8.x branch has no Dynamic Content Filter addon at all, and it runs to the end of the 5.x line because 5.7.2 still prints the value unescaped. The 6.x branch escapes both values. Fix: on Joomla 4, 5 or 6, update to the current SP Page Builder 6.x release. On Joomla 3, SP Page Builder 5.6.1 can take JoomShaper's Joomla 3 Security Patch 1.0.3, which escapes both values but does not change the reported version, so a 5.6.1 site with 1.0.3 applied still shows here; the Unpatched JoomShaper Security Holes tool reports which patch release is actually installed. Until you can update, remove the Dynamic Content Filter addon from public pages.

Is my site affected?

Affected
SP Page Builder from 5.5.0 up to but not including 6.0.0
Fixed in
6.0.0
What to do
Update SP Page Builder to 6.0.0 for this flaw, or to 6.9.1 or later, which no rule we check matches.
Check whether your sites are affected

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

5.3 Medium

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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: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:L Confidentiality
Low. Some data can be read
VI:L Integrity
Low. Some data can be altered
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. 2 October 2026We published: SP Page Builder's Joomla 3 Security Patch Was Incomplete. Version 1.0.3 Fixes It.
  2. 5 October 2026CVE-2026-102426 record published by its CNA
  3. 5 October 2026mySites.guru check added for SP Page Builder (from 5.5.0 up to but not including 6.0.0)

Rule details

Our disclosure post

SP Page Builder's Joomla 3 Security Patch Was Incomplete. Version 1.0.3 Fixes It.

SP Page Builder's Joomla 3 Security Patch Was Incomplete. Version 1.0.3 Fixes It.

JoomShaper's first Joomla 3 security patch for SP Page Builder left the captcha bypass live and the XSS fix incomplete. Version 1.0.3 closes both.

Other vulnerabilities in SP Page Builder

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

SP Page Builder

Latest safe version: 6.9.1

All 17 CVEs in SP Page Builder

References

CVE-2026-102426 questions

Which versions are affected by CVE-2026-102426?
CVE-2026-102426 affects SP Page Builder from 5.5.0 up to but not including 6.0.0. The fix is in 6.0.0.
How do I fix CVE-2026-102426?
Update SP Page Builder to 6.0.0 for this flaw, or to 6.9.1 or later, which no rule we check matches. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
How severe is CVE-2026-102426?
Joomla CNA scores it 5.3 (Medium) 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 8 October 2026.