CVE-2026-34233
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. In versions 1.1.1 and prior, multiple admin controllers expose DataTable endpoints without authorization checks, allowing any authenticated user to access sensitive administrative data that should be restricted to administrators only. The affected admin controllers define datatable() methods that are reachable via GET requests but lack any permission or role verification. Because the routes fall under the /admin/ prefix, operators may assume they are protected - however, the middleware applied to this route group does not enforce admin-level authorization on these specific endpoints. As a result, any authenticated user (regardless of role) can query these endpoints and receive paginated JSON responses containing sensitive records. Exploitation can result in enumeration of user PII, payment and transaction records, active voucher and coupon codes, role and permission structure, server ownership mappings and support ticket contents. 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 confidenceInsecure Direct Object Reference (IDOR) vulnerability in CtrlPanel billing software where multiple admin controller DataTable endpoints lack authorization checks, allowing any authenticated user to access admin-only data including PII, payment records, vouchers, roles, server ownership, and support tickets despite being under the /admin/ route prefix.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed CtrlPanel versionLocate the version file or check the application header/footer for the version number. Common paths include VERSION file, composer.json, or the admin dashboard 'About' page.Affected if Installed version is 1.1.1 or any version prior to 1.2.0
-
Confirm user authentication is enabledVerify that the application requires login for access. Check if unauthenticated requests to any /admin/ route are redirected to a login page.Affected if Authentication is required but role verification on admin endpoints is not enforced
-
Locate DataTable endpoints under /admin/Review application routes or use a web proxy to enumerate endpoints matching patterns like /admin/*/datatable, /admin/users/datatable, /admin/payments/datatable, /admin/vouchers/datatable, /admin/tickets/datatable, /admin/roles/datatable.Affected if DataTable endpoints exist under the /admin/ prefix and are accessible to authenticated users
-
Test authorization on admin DataTable endpointsLog in as a non-admin or low-privilege user (e.g., regular customer account) and attempt to access admin DataTable endpoints. Use curl or a browser to send authenticated requests to /admin/users/datatable, /admin/payments/datatable, or similar paths.Affected if Non-admin accounts can successfully retrieve sensitive data from admin endpoints (HTTP 200 with JSON data returned)
-
Verify role verification on /admin/ route groupExamine the application's route middleware or controller code to check if the /admin/ route group or individual DataTable endpoints enforce admin role checks.Affected if No role-based authorization middleware is applied to the admin DataTable endpoints
You are affected if CtrlPanel version 1.1.1 or prior is installed and non-admin users can access DataTable endpoints under /admin/ to retrieve sensitive administrative data.
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 version 1.2.0 which contains the authorization fix; for immediate mitigation, add role-based access control middleware to all affected datatable() methods in admin controllers to verify admin privileges before returning data.
1.2.0
- Upgrade CtrlPanel from version 1.1.1 (or any prior version) to version 1.2.0 to resolve the improper access control vulnerability in admin DataTable endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34233 — 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-34233 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