CVE-2026-62414
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 - Improper access control in Page Builder CK < 3.6.2 - The Joomla extension Page Builder CK does not properly apply access control to frontend page list views.
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 confidenceThe Page Builder CK Joomla extension versions prior to 3.6.2 contain an improper access control vulnerability where the frontend page list views do not properly enforce access restrictions. This allows unauthorized users to potentially view pages they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Verify Page Builder CK extension is installedIn Joomla admin, go to Extensions > Manage > Manage and search for 'Page Builder CK' or 'pagebuilderck' to confirm the extension is installedAffected if Page Builder CK is not found in the extensions list, then this CVE does not apply
-
Identify the installed version of Page Builder CKIn Joomla admin, go to Extensions > Manage > Manage, find Page Builder CK, and note the version column. Alternatively, check the extension's manifest file in /administrator/manifests/files/ or the component directory for version informationAffected if The installed version is unknown or cannot be determined, treat it as potentially affected
-
Compare installed version to the affected rangeCompare the identified version number to 3.6.2. The affected range is any version before 3.6.2 (e.g., 3.6.1, 3.6.0, 3.5.x, etc.)Affected if The installed version is 3.6.1 or lower, or any version number less than 3.6.2, the environment is affected by this CVE
-
Confirm frontend page list view is accessibleVisit the frontend page list URL endpoint for Page Builder CK (typically /index.php?option=com_pagebuilderck or similar route) while logged in as a low-privilege or unauthorized user to test if page content is exposedAffected if Frontend page list view displays page content to users without proper permissions, confirming the access control flaw is present and exploitable
The environment is affected if Page Builder CK is installed with a version lower than 3.6.2 and the frontend page list view exposes content to unauthorized users.
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.
From vendor dataUpgrade Page Builder CK extension to version 3.6.2 or later to resolve the access control flaw.
- 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-62414 — 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-62414 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