VulnerabilityPublished 14 Sep 2026Updated 5 Oct 2026

CVE-2026-79701: joomshaper.com SP Page Builder (Pro) extension for Joomla · Reliance on Untrusted Inputs in a Security Decision

Affects joomshaper.com SP Page Builder (Pro) extension for JoomlaSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
joomshaper.comSP Page Builder (Pro) extension for Joomla	Affected =3.2.6 - 5.6.1p2 =6.0.0 - 6.9.0	Fixed in–

AI-suggested

Until a fix is available, avoid placing the affected addons inside SP Page Builder modules or restrict access to forms that rely on CAPTCHA verification. Monitor vendor communications for official patches or updates addressing this issue.

Description

CVE-2026-79701 is a vulnerability in the SP Page Builder (Pro) extension for Joomla by joomshaper.com that allows unauthenticated CAPTCHA bypass in certain addons. The flaw occurs because the CAPTCHA verification result is discarded and replaced with a simple non-empty string check when the request includes the parameter view_type=module. This allows attackers to bypass CAPTCHA protections in the ajax_contact, optin_form, and form_builder addons when used inside an SP Page Builder module, regardless of the CAPTCHA type configured. The view_type parameter is not validated against the actual rendering context of the form, enabling this bypass.

Impact

An attacker can bypass CAPTCHA protections in the affected addons without authentication, potentially enabling automated or spam submissions through contact, opt-in, or form builder forms. This reduces the effectiveness of CAPTCHA as a defense mechanism, increasing the risk of abuse or spam. However, the vulnerability does not require privileges or user interaction and has no direct code execution or data disclosure impact described.

Summary

The vulnerability affects the SP Page Builder (Pro) extension for Joomla, specifically versions 3.2.6 - 5.6.1p2 and 6.0.0 - 6.9.0, in the ajax_contact, optin_form, and form_builder addons. When these addons are placed inside an SP Page Builder module, the CAPTCHA plugin's onCheckAnswer event result is ignored and replaced by a test for any non-empty string if the request parameter view_type equals 'module'. This allows an attacker to submit any arbitrary token with view_type=module and pass CAPTCHA verification without proper validation. The root cause is reliance on untrusted input (view_type parameter) in a security decision, classified as CWE-807.

CWE-807Reliance on Untrusted Inputs in a Security Decision (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
Architecture and Design · Attack Surface Reduction
Store state information and sensitive data on the server side only.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

joomshaper.com/joomla-extensions/sp-page-builder-pro (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Oct 2026, 19:09 UTC

WeaknessesCWE-807

Technical details

References

Community reviews

Related threats