Improper Access ControlWeakness · CWE-284

CVE-2026-47366

HIGH · 7.2 CVSS v3.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper verification of access permissions when modifying permissions through the Administration Control Panel (ACP) allowed an authenticated administrator to grant permissions beyond the level authorized for their account, resulting in privilege escalation within the administrative interface.

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 confidence

The Administration Control Panel (ACP) fails to properly validate whether an authenticated administrator has sufficient privileges to grant specific permissions. By submitting permission modification requests through the ACP, a lower-privileged admin can assign themselves or others permissions exceeding what their account is authorized to manage, enabling privilege escalation within the administrative interface.

MitigationImplement server-side authorization checks that verify the requesting administrator has the required permission-level authority before allowing any permission modifications, and enforce role-based permission boundaries in the ACP permission management logic.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if your system has an Administration Control Panel (ACP)
    Locate and access your system's admin interface, typically found at /admin, /acp, /administrator, or similar paths defined in your web server configuration. Confirm the presence of a permission or role management module within the ACP.
    Affected if Your system uses an ACP with permission management capabilities and you have administrator accounts with varying privilege levels.
  2. Verify authorization enforcement on permission modification endpoints
    Inspect the server-side code handling permission change requests in the ACP (look for request handlers for roles, permissions, or access control). Check that the code validates the requesting admin's privilege level BEFORE processing any permission modifications.
    Affected if The permission modification logic does not verify the requesting administrator has authority to grant the specific permission being requested.
  3. Review admin audit logs for unauthorized permission changes
    Search your application and system logs for events involving permission grants, role assignments, or access level modifications. Look for entries where a lower-privileged admin account modified permissions beyond their authorized scope.
    Affected if Audit logs show permission modifications performed by administrators whose own permissions should not allow them to grant such privileges.
  4. Check for role-based permission boundaries in ACP configuration
    Examine your ACP permission management settings or database tables storing role-permission mappings. Verify that each admin role has clearly defined boundaries and that the system enforces these boundaries when permission requests are submitted.
    Affected if The system allows administrators to modify permissions outside their defined role boundaries without proper authorization checks.
  5. Compare your admin role definitions against expected privilege constraints
    Review all defined administrator roles and their assigned permissions in your system. Identify any roles that can modify permissions without restriction or that lack explicit authorization validation logic.
    Affected if Admin roles exist that can grant elevated permissions without the system validating the requester's own permission level for that specific action.

Your environment is affected if the ACP allows any authenticated administrator to modify permissions beyond what their role should authorize, without server-side validation of their privilege level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side authorization checks that verify the requesting administrator has the required permission-level authority before allowing any permission modifications, and enforce role-based permission boundaries in the ACP permission management logic.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47366 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47366 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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