A defensive advisory for a vulnerability with confirmed in-the-wild exploitation (listed in CISA KEV). What happens, what's affected, and how to respond — with no attack how-to or proof-of-concept. For the durable design-level defense, see file upload vulnerabilities and how to defend.
- CVE
- CVE-2026-48908
- Severity
- Critical (CVSS 10.0 / v4.0 from the CVE numbering authority; NVD rates it CVSS v3.1 9.8) — actively exploited (CISA KEV)
- Type
- Unauthenticated arbitrary file upload → RCE (CWE-434)
- Impact
- Remote code execution (RCE) with no authentication
- Affected
- SP Page Builder for Joomla (JoomShaper) — 6.6.1 and earlier
- Main fix
- Update to 6.6.2 or later
Reached with no authentication
Arbitrary file upload
Lands somewhere it can execute
Remote code execution
Fix: update to 6.6.2 or later
Why not-patching is dangerous
Because RCE is reachable without authentication, it's a prime target for automated mass scanning (which is why it made the KEV list). Censys measured well over a hundred thousand internet-facing properties running SP Page Builder, and affected versions were attacked on a large scale. "We're too small to be targeted" does not hold.
What's affected
| Item | Detail |
|---|---|
| Extension | SP Page Builder for Joomla (JoomShaper) |
| Affected versions | 6.6.1 and earlier |
| Fixed version | 6.6.2 and later |
| Precondition | No authentication required |
| Reachable impact | Remote code execution (RCE); data theft |
A note on patch completeness (both sides, unresolved)
6.6.2 is reported to close the actively-exploited path (the custom-icon upload). Separately, a community report claimed a secondary path (part of the admin-side handling) still lacked an authentication check in 6.6.2; in response the vendor (JoomShaper) is reported to have disputed it — saying the editor-side controller enforces authentication first — while indicating a fix in a following update. As this is not settled, update to 6.6.2, keep defense-in-depth in place, and watch for the next release (6.6.x).
How to respond
Update to 6.6.2+ (top priority)
Check for compromise (assume you were reached before updating)
Temporary defense until you can update (defense-in-depth)
Inventory extensions + machine-monitor CVEs
This site's take: prevent the whole pattern by design, not just this CVE
This incident is one instance of a common pattern — "unauthenticated upload → RCE" (a sibling Joomla extension, CVE-2026-56290, was exploited the same way in the same period). The single update is mandatory, but what pays off long-term is designing the pattern out: authenticate the upload endpoint, allow-list plus content-inspect server-side, and store outside the web root or disable execution. See file upload vulnerabilities and how to defend.
Read next
- Defense (durable): file upload vulnerabilities — designing out web shells / RCE
- Same pattern, alert: CVE-2026-48939 (iCagenda / Joomla unauthenticated upload → RCE)
- Glossary: what RCE (remote code execution) is / what a CVE is
- All alerts: vulnerability alerts