CVE-2026-77994 is a critical vulnerability in Page Builder CK, a widely used page-building extension for Joomla websites. If your organization operates a Joomla site that uses this extension, an attacker may be able to interact with your website database without valid credentials, potentially exposing customer records, altering website content, or disrupting operations.
This issue matters because many organizations treat a website as a marketing asset rather than a business system that holds sensitive data. In reality, a compromised public website can become an entry point into customer information, internal workflows, payment-related processes, and brand trust.
This post explains what CVE-2026-77994 means for your business, which organizations should investigate it immediately, and how to respond. It also includes a technical appendix for security engineers, penetration testers, and IT teams responsible for remediation.
CVE-2026-77994 was published on August 24, 2026, by the Joomla! Project as the assigned CVE Numbering Authority. The affected product is Page Builder CK, a Joomla extension developed by joomlack.fr. Versions 1.0.0 through 3.6.4 are affected, and version 3.6.5 is the fixed release.
The vulnerability is a second-order SQL injection in the loadStyles method of the extension’s frontend page model. In plain language, data that can be stored through the website may later be used in a database query in a way that changes the query’s intended behavior. The issue is rated critical, with a CVSS v4.0 base score of 9.3.
The key response milestone is the release of Page Builder CK 3.6.5. Organizations running any earlier release should treat the extension as potentially exploitable until they have confirmed the updated version is installed and functioning correctly.
If your Joomla website uses an affected version of Page Builder CK, the primary risk is unauthorized access to the database behind your website. That database may contain more than published pages. Depending on your configuration, it can include user accounts, contact-form submissions, customer details, order or membership records, internal notes, and credentials for website administrators.
The operational impact can be immediate. An attacker could deface pages, insert malicious content, redirect visitors, remove published material, or interfere with forms and checkout processes. For a business that relies on its website to generate leads, take bookings, process inquiries, or support customers, even a short period of disruption can translate into lost revenue and delayed service.
There is also a data protection concern. If personal information is stored in the Joomla database, unauthorized access may create notification, investigation, and regulatory obligations under applicable privacy laws in the United States and Canada. The precise duties depend on the data involved, your industry, and your jurisdiction, but the cost of responding after an incident is almost always higher than the cost of timely patching.
Finally, a compromise can damage trust. Customers, partners, and regulators expect organizations to maintain basic security hygiene for public-facing systems. A visible website compromise can undermine confidence in your broader security program, even if the underlying issue was limited to one third-party extension.
Regional professional-services firm: A firm uses Joomla for its public site and stores inquiries from prospective clients in the database. An attacker exploits the flaw to extract submission records containing names, email addresses, phone numbers, and project descriptions. The firm must notify affected individuals, investigate the exposure, and rebuild client confidence after a preventable extension vulnerability.
Mid-sized healthcare marketing organization: A healthcare marketing company hosts appointment-request forms and educational content on Joomla. Exploitation allows an attacker to alter pages and inject misleading content. Although clinical systems are not directly affected, patients and referral partners question whether the organization can protect sensitive information.
E-commerce retailer using Joomla for content and promotions: A retailer uses Page Builder CK for campaign landing pages while its storefront handles transactions separately. An attacker manipulates promotional pages and redirects visitors to a fraudulent page. The direct database exposure may be limited, but abandoned carts, support volume, and brand damage still create measurable business loss.
Municipal or nonprofit website: A public-sector or nonprofit organization uses Joomla to publish notices, program information, and contact forms. An attacker modifies official announcements or harvests resident-submitted information. The organization faces public scrutiny, service disruption, and the administrative burden of demonstrating that its systems are secure.
If any of these statements applies, prioritize verification and remediation. The affected range is broad, and the vulnerability does not require an authenticated user according to its published severity rating.
If you operate a Joomla website, do not wait for a security alert to confirm whether Page Builder CK is present and current. IntegSec can help you identify exposed web applications, validate the vulnerability, assess evidence of exploitation, and test the effectiveness of your remediation. Our penetration testing team focuses on practical risk reduction for organizations across the United States and Canada. Visit https://integsec.com to schedule a conversation about protecting your web estate.
CVE-2026-77994 is a second-order SQL injection vulnerability in the Page Builder CK extension for Joomla, developed by joomlack.fr. The weakness resides in the loadStyles method of the extension’s frontend page model. Attacker-influenced data can be persisted and subsequently incorporated into a SQL query without adequate parameterization or contextual validation, enabling malicious SQL execution when that stored value is processed.
The affected component is the Page Builder CK extension, commonly identified as com_pagebuilderck, rather than the Joomla core itself. Affected versions are 1.0.0 through 3.6.4; version 3.6.5 contains the fix. The vulnerability is classified as CWE-89, Improper Neutralization of Special Elements used in an SQL Command.mcpsec+2
The published CVSS v4.0 vector is 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, producing a critical base score of 9.3. This indicates network exploitation, low attack complexity, no privileges required, no user interaction required, and high potential impact to confidentiality, integrity, and availability. The NVD entry is available at https://nvd.nist.gov/vuln/detail/CVE-2026-77994.
Version enumeration should begin with an inventory of installed Joomla extensions. Administrators can review the Joomla administrator console under System → Install → Extensions or query the #__extensions table for the Page Builder CK component and its configured version. Command-line operators with database access can use:
Scanner signatures should test for the presence of Page Builder CK and flag versions below 3.6.5. Authenticated configuration checks are preferable to blind exploitation, particularly in production. Vulnerability scanners and CMS inventory tools should be configured to identify the extension by its component name, manifest metadata, and disclosed version range.
Log indicators may include unusual SQL errors, unexpected database query volume, requests referencing Page Builder CK frontend routes, or queries containing SQL control characters. Behavioral anomalies include new administrator accounts, modified page content, unexpected redirects, unfamiliar files in the web root, altered database records, and outbound connections from the web server that do not correspond to known integrations. Network exploitation indicators include anomalous POST requests to Page Builder CK endpoints, repeated requests from a single source followed by database errors, and traffic patterns inconsistent with normal content browsing.
Official vendor remediation should take precedence over compensating controls. Interim mitigations reduce exposure but do not correct the insecure handling of stored data in the vulnerable loadStyles code path.