Skip to main content
VulnerabilityPublished Updated

CVE-2026-74254: joomlack.fr Page Builder CK extension for Joomla · SQL Injection

Affects joomlack.fr Page Builder CK extension for JoomlaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical · fixed in 3.6.5 : patch joomlack.fr Page Builder CK extension for Joomla as a priority.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
joomlack.frPage Builder CK extension for JoomlaAffected
  • =1.0.0-3.6.4
Fixed in–

AI-suggested

Upgrade the Page Builder CK extension to version 3.6.5 or later to ensure the backend is patched, and at least version 3.6.4 for the frontend. These versions contain official fixes that address the SQL injection vulnerability. No additional mitigation is required once the extension is updated.

Description

The Joomla extension Page Builder CK versions up to 3.6.4 are vulnerable to an SQL injection flaw affecting the styles model. This vulnerability allows an attacker to execute arbitrary SQL commands due to improper neutralization of special elements in SQL queries. The issue was fixed in version 3.6.5 for the backend and in 3.6.4 for the frontend.

References

Community reviews

Loading reviews…