Page Builder CkApplication · Joomlack
CVE-2026-56290
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJoomla Extension - joomlack.fr - Unauthenticated file upload in Page Builder CK extension < 3.6.0 - The Joomla extension Page Builder CK is vulnerable to an unauthenticated arbitrary file upload that allows uploading executable files and leads to full RCE.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnauthenticated arbitrary file upload vulnerability in Page Builder CK extension for Joomla allows remote attackers to upload executable files without authentication, achieving full remote code execution. The vulnerability affects versions prior to 3.6.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Page Builder CkApplication
< 3.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Page Builder CK extension is installedLog into Joomla administrator panel and navigate to Extensions > Manage. Search for 'Page Builder CK' or 'Joomlack' to verify the extension is present and enabled.Affected if The extension is listed as installed and enabled in Joomla
-
Identify installed version numberIn Joomla admin, go to Extensions > Manage, find Page Builder CK, and note the version column. Alternatively, check the extension's XML manifest file in /administrator/components/com_pagebuilderck/ or /components/com_pagebuilderck/Affected if Version is less than 3.6.0 (e.g., 3.5.x, 3.4.x, earlier versions)
-
Locate upload directoriesCheck the extension configuration or component files for upload paths. Common locations may include /images/pagebuilderck/ or /media/pagebuilderck/uploads/ within the Joomla installation.Affected if Upload directories exist and are web-accessible
-
Inspect upload directories for suspicious filesList files in the extension's upload directories using file manager or command line. Look for unexpected file types such as .php, .phtml, .phar, .js files with unusual names or recent creation dates.Affected if Unexpected executable files (especially .php) are present in upload directories
-
Review web server access logsExamine Apache/Nginx access logs for POST requests to page builder upload endpoints. Look for requests to paths like /index.php?option=com_pagebuilderck or /components/com_pagebuilderck/ from unknown IP addresses.Affected if Unauthenticated POST requests to upload functionality are logged
If Page Builder CK version is below 3.6.0 and the extension is enabled, the environment is vulnerable to unauthenticated arbitrary file upload and remote code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.6.0
Upgrade Page Builder CK to version 3.6.0 or later. If immediate patching is not feasible, disable the extension or implement web server-level access restrictions to block unauthorized access to the extension's upload functionality.
Page Builder CK 3.6.0
- Back up your Joomla site and database before performing any updates
- Download Page Builder CK version 3.6.0 or later from the official source (www.joomlack.fr)
- Navigate to Joomla Administrator > Extensions > Install
- Upload and install the Page Builder CK 3.6.0 package
- Verify the extension shows version 3.6.0 or later in Extensions > Manage
- Confirm the site and extension functionality are working correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Page Builder Ck
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data