Quick answers
- Is CVE-2026-78375 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78375 being exploited in the wild.
- How severe is CVE-2026-78375?
- Informational severity, with a CVSS score of 6.5, published 14 September 2026.
- Which products and versions are affected?
- JoomShaper SP Page Builder 5.2.1 to 6.9.0.
- Is there a fix for CVE-2026-78375?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78375 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-78375?
- Check whether you run JoomShaper SP Page Builder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authenticated SQL injection in the plgContentSppagebuilder::onContentAfterSave() method. The plugin reads the jform[attribs][sppagebuilder_article_id] parameter from the request and concatenates it directly into a WHERE clause without quoting or type casting. Because Joomla's ARRAY input filter does not sanitize individual array element values, an attacker can deliver a complete SQL injection payload in a single POST field. The vulnerable code executes on every onContentAfterSave event before component-level access checks, allowing exploitation regardless of context. An attacker can perform time-based blind SQL injection to extract arbitrary database contents from tables such as #__users and #__session.
Affected products
- JoomShaper SP Page Builder 5.2.1 to 6.9.0
Timeline
- 2026-09-14: disclosed: CVE-2026-78375 published