CVE-2026-34358
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 · uneditedCtrlPanel is open-source billing software for hosting providers. Versions 1.1.1 and prior contains a broken access control vulnerability where multiple admin controllers enforce permission checks on form display methods but omit equivalent checks on the corresponding write methods, allowing any authenticated user to bypass RBAC via direct POST/PATCH requests. Controllers missing checks on write methods store() and update() include ApplicationApiController (admin.api.write), CouponController (admin.coupons.write), PartnerController (admin.partners.write), ShopProductController (admin.store.write), UsefulLinkController (admin.useful_links.write), and VoucherController (admin.voucher.write); ProductController (admin.products.edit), ServerController (write/change_owner/change_identifier), and UserController (write/change_email/change_credits/change_username/change_password/change_role/change_referral/change_ptero/change_serverlimit) are missing checks on update() only, and ActivityLogController exposed empty stub store()/update() methods that silently accepted any request. An authenticated attacker without admin write privileges can issue API credentials, generate unlimited coupons and vouchers, assign arbitrary partner commission and discount rates, alter shop product pricing and limits, reassign server ownership or identifiers, and modify user accounts including roles, credits, passwords, and linked Pterodactyl IDs to achieve full privilege escalation, as well as abuse logBackIn() without the login_as permission to interfere with admin impersonation sessions. This issue has been fixed in version 1.2.0.
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 confidenceCtrlPanel versions 1.1.1 and prior suffer from broken access control where multiple admin controllers enforce permission checks on form display methods but omit equivalent checks on corresponding write methods (store(), update()), allowing authenticated non-admin users to perform privileged actions via direct POST/PATCH requests to endpoints managing API credentials, coupons, vouchers, partners, shop products, servers, and user accounts including role escalation.
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
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify CtrlPanel versionLocate the version file or admin dashboard version display (commonly in config files, composer.json, or admin footer). Compare the installed version to the 1.2.0 fixed release.Affected if Installed version is below 1.2.0 (e.g., 1.0.x, 1.1.x)
-
Locate admin controllersFind the admin controller files in the application source code. Look for controllers handling users, roles, credits, coupons, vouchers, API credentials, and servers.Affected if Admin controllers exist and are accessible to the application
-
Verify permission enforcement on write methodsExamine the store() and update() methods in admin controllers. Check if they contain authorization checks (e.g., middleware, $this->authorize(), permission validation) matching those on display/index methods.Affected if store()/update() methods lack permission checks while corresponding display methods have them
-
Test non-admin access to admin write endpointsUsing an authenticated non-admin user session, attempt POST/PUT/DELETE requests to admin endpoints (e.g., /admin/users/store, /admin/roles/update, /admin/credits/update). Observe if requests succeed without permission errors.Affected if Non-admin authenticated users can successfully execute admin store/update operations
You are affected if CtrlPanel version is below 1.2.0 AND non-admin users can perform admin-level write operations without proper authorization checks on store()/update() methods.
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 · scopedUpgrade to CtrlPanel version 1.2.0 which contains the fixed access control enforcement, or implement permission checks on all store() and update() methods in the affected controllers.
1.2.0
- Upgrade CtrlPanel from version 1.1.1 or prior to version 1.2.0
- After upgrading, verify that proper permission checks are now enforced on all write methods (store, update) across the affected controllers
- Test that authenticated non-admin users can no longer bypass RBAC via direct POST/PATCH requests to admin endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34358 — 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-34358 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