/

CVE-2026-84715

Severity:

HIGH RISK

(8.8)

Improper Authorization (CWE-862) in FeatherPanel Subusers

CVE-2026-84715

Deferred

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-862

Impact:

Privilege Escalation and Unauthorized Access

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

FeatherPanel contains an authorization flaw in the SubuserController updateSubuser handler that allows authenticated subusers to alter their own permission records. A subuser with limited access may therefore grant themselves broader server privileges and access sensitive data, backups, or configuration.

Affected context

The issue occurs in FeatherPanel deployments where subusers can reach the updateSubuser functionality and the handler does not independently verify whether the requesting account is authorized to change permission records. It is most relevant when a low-privilege subuser can submit account or permission updates that are trusted without enforcing ownership and administrative authorization boundaries.

Exploit preconditions

  • Attack surface: The authenticated SubuserController updateSubuser handler
  • Required access: A valid FeatherPanel subuser account, potentially with minimal permissions
  • Trigger point: Processing a request that updates the subuser's permission records
  • Why exploitation is possible: The handler fails to adequately validate whether the requester is authorized to modify those permissions, allowing self-directed privilege changes

Why this happens

The underlying bug is an authorization decision failure in which the application accepts a subuser's request to modify security-sensitive permission data without enforcing the required privilege boundary. This maps to CWE-862, Improper Authorization: authentication establishes the requester's identity, but the authorization logic does not correctly verify whether that identity may perform the requested operation or alter the targeted permission attributes.

Potential impact

  • A subuser may gain administrative or full server control
  • Attackers could access sensitive application or server data
  • Backups may be viewed, altered, or removed
  • Server configuration could be exposed or changed
  • Compromised accounts could support persistence or further lateral movement

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side

operation and field level rather than relying on client-provided role or

permission values.

Common defensive patterns include:

  • Require explicit administrative authorization for permission changes
  • Prevent subusers from modifying their own roles or privilege attributes
  • Apply deny-by-default checks to sensitive account-management operations
  • Enforce object-level and field-level authorization independently
  • Derive effective permissions from trusted server-side state
  • Run security-sensitive actions with the minimum required application privileges
  • Record and review permission changes, including the actor and affected account

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying controller methods that update roles or permissions without an authorization guard
  • Code review checks for self-service account changes involving privilege-bearing fields
  • Tests that verify low-privilege users cannot modify their own or another user's permissions
  • API policy enforcement requiring elevated roles for account and access-control mutations
  • Audit-log monitoring for unexpected privilege changes or permission updates initiated by subusers
  • Automated application security testing that exercises object-level and field-level authorization boundaries

Sources

SourceLink
github.comgithub.com/MythicalLTD/FeatherPanel
github.comgithub.com/MythicalLTD/FeatherPanel/blob/376b003aa9685b74153d239d2b3f64a752cdc0f0/backend/app/Controllers/User/Server/SubuserController.php#L454
github.comgithub.com/MythicalLTD/FeatherPanel/blob/376b003aa9685b74153d239d2b3f64a752cdc0f0/backend/app/Helpers/ServerGateway.php
github.comgithub.com/MythicalLTD/FeatherPanel/commit/06ef8dcac471201748516ca743694159cb846a9d
github.comgithub.com/MythicalLTD/FeatherPanel/releases/tag/v1.3.7.10
vulncheck.comvulncheck.com/advisories/featherpanel-before-1.3.7.10-privilege-escalation-via-subuser-permission-update

Frequently asked

questions

It may be exploitable through the FeatherPanel application interface by an

authenticated subuser, depending on network exposure and deployment access

controls. It does not generally require unauthenticated network access.

The attacker needs a valid subuser account that can reach the affected

update operation. Extensive permissions should not be required if the

authorization boundary is incorrectly enforced.

Enforce server-side authorization for every permission change and explicitly

deny subusers the ability to modify their own privilege-bearing attributes.

Use centralized access-control checks, test both object-level and field-level

authorization, apply deny-by-default policies, and monitor audit logs for

unexpected privilege changes.

Find out what's already
exploitable in your codebase.