JoomShaper SP Page Builder Extension up to 6.9.0 Content Plugin onContentAfterSave sppagebuilder_article_id sql injection

Summaryinfo

A vulnerability, which was classified as problematic, has been found in JoomShaper SP Page Builder Extension up to 6.9.0. Affected is the function plgContentSppagebuilder::onContentAfterSave of the component Content Plugin. The manipulation of the argument sppagebuilder_article_id leads to sql injection. This vulnerability is listed as CVE-2026-78375. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in JoomShaper SP Page Builder Extension up to 6.9.0. It has been rated as problematic. This issue affects the function plgContentSppagebuilder::onContentAfterSave of the component Content Plugin. The manipulation of the argument sppagebuilder_article_id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Joomla Extension - joomshaper.com - Authenticated Privileged SQL Injection in the Content Plugin of SP Page Builder (Free and Pro) 5.2.1 - 6.9.0 - plgContentSppagebuilder::onContentAfterSave() read jform[attribs][sppagebuilder_article_id] from the request and concatenated it directly into the WHERE view_id = ... clause of a query against #__sppagebuilder without quoting or type casting. Joomla's ARRAY input filter does not sanitise element values, as InputFilter::clean() returns (array) $source with the elements untouched, so the entire payload could be delivered in a single POST field. The affected block also executed before the com_content.article context test, so it ran on every onContentAfterSave event regardless of which component triggered the save. An attacker could perform time-based blind SQL injection to read arbitrary database contents, including the #__users and #__session tables.

It is possible to read the advisory at joomshaper.com. The identification of this vulnerability is CVE-2026-78375 since 08/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/14/2026). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• JoomShaper

Name

• SP Page Builder Extension

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion