CVE-2026-57518
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 · uneditedPagekit CMS 1.0.18 contains a privilege escalation vulnerability that allows authenticated users with the 'user: manage users' permission to escalate privileges by assigning arbitrary custom roles to themselves due to missing authorization checks in UserApiController::saveAction(). Attackers can assign themselves a custom role with the 'system: manage packages' permission and then upload and install a malicious PHP package through the admin package installer to achieve remote code execution.
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 confidencePagekit CMS 1.0.18 has a privilege escalation vulnerability in UserApiController::saveAction() where missing authorization checks allow authenticated users with 'user: manage users' permission to assign themselves arbitrary custom roles. Attackers can assign a role with 'system: manage packages' permission and achieve RCE by uploading a malicious PHP package.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Pagekit CMS installation and versionLocate the Pagekit installation and identify the version number. Check version.php, composer.json, or the admin dashboard About page for version 1.0.18.Affected if The installed version is 1.0.18.
-
Verify UserApiController exists in the installationLocate the file UserApiController.php within the Pagekit source code, typically under the user management or API component directory.Affected if The file exists and lacks authorization checks in the saveAction() method.
-
Identify users with 'user: manage users' permissionQuery the user permissions table or access the admin panel user management section to list accounts granted the 'user: manage users' permission.Affected if Any authenticated user account possesses this permission.
-
Check for roles containing 'system: manage packages' permissionExamine the role definitions in the database or admin panel to identify custom or existing roles that include the 'system: manage packages' permission.Affected if Such a role exists and can be assigned by a user with 'user: manage users' permission.
-
Verify package upload/install functionality is accessibleConfirm that the package management feature allows uploading or installing new packages, typically found in the Extensions or Packages section of the admin panel.Affected if The package installation feature is enabled and accessible to users who can obtain the 'system: manage packages' permission.
A user is affected if running Pagekit CMS version 1.0.18 and any account has the 'user: manage users' permission that can be leveraged to assign a role with 'system: manage packages' permission for package upload and RCE.
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 dataImplement proper authorization checks in UserApiController::saveAction() to validate that users cannot assign roles with permissions beyond their current scope, and restrict custom role assignment to prevent privilege escalation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57518 — 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-57518 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