Join our Newsletter — 33% off our NHI Course
Authentication, Authorisation & Trust

CWE-863

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Authentication, Authorisation & Trust

CWE-863 is a weakness category for incorrect authorisation. It covers cases where software allows a user or process to access data or actions outside its intended permissions, often because the application fails to check ownership, role or scope before returning a result or performing an operation.

What incorrect authorisation means in practice

CWE-863 describes a class of access-control weakness where software makes a decision without correctly checking whether the caller should be allowed to see or do that specific thing. The defect is usually not in the business idea itself, but in the enforcement step, for example when ownership, role, tenant, object, or scope is not validated before a record is returned or an operation is executed.

This weakness is especially important because it can look like normal application behaviour until a request is made for something that should have stayed out of reach. In APIs, web apps, services, and back-end workflows, the failure often sits at the boundary between a valid session and the wrong entitlement decision.

Why CWE-863 creates security exposure

Incorrect authorisation can expose private records, let a user act on another user's object, or allow a process to trigger operations it was never meant to perform. The impact is often broader than a single broken page because the same flawed check may be reused across many endpoints or code paths.

Because the weakness concerns enforcement rather than identity proofing, attackers usually do not need to break authentication first. They may only need a valid account, a predictable object identifier, or an alternate path that skips the intended permission check. This makes the flaw a common route to data exposure and unintended state changes.

In well-built systems, authorisation should be tied to the specific resource and action, not just to the fact that a user is signed in. That is why this weakness often shows up as missing object-level checks, missing function-level checks, or inconsistent scope validation across features.

Where this weakness typically appears

CWE-863 is most often found in application back ends, APIs, service layers, and administrative interfaces where one request can reference another user's object, tenant, or job. It can also appear in batch tooling or internal workflows when a process assumes that any authenticated caller is trusted to use a function or data set.

The pattern is often subtle: one code path checks permissions correctly, while another path calls the same action handler without the same guard. That inconsistency is why testing needs to follow the actual business objects and actions, not just the login flow.

When reviewing exposure, focus on whether the application enforces permission at the point of use, and whether the rule is consistent across direct requests, API calls, background jobs, and privileged interfaces. A single missed check can create a reusable bypass.

How teams reduce and detect incorrect authorisation

Reducing this weakness starts with designing authorisation around the resource, action, and context, then applying that rule uniformly wherever the operation can be reached. Strong review habits are important too, especially for endpoints that accept object identifiers, role changes, exports, deletes, or cross-tenant queries.

Detection is usually a mix of code review, security testing, and telemetry. Testers should try object tampering, role switching, scope changes, and alternate request paths to see whether the same decision is enforced everywhere. Logging should preserve enough context to show who attempted which action, against which object, and whether the decision was denied or allowed.

For teams that want a broader mapping of this weakness family, the CWE Top 25 Guide explains how high-impact software weaknesses are prioritised and why missing authorisation checks belong on that short list. The relationship between weakness classes and vulnerability records is also covered in the CVE, CWE and CPE Guide, which is useful when translating a code flaw into a vulnerability-management workflow.

Risk and Threat Considerations

Incorrect authorisation is attractive to attackers because it can turn ordinary application access into access to someone else’s data or functions. The most common risk is silent privilege expansion, where a weak check lets a caller read, modify, delete, or trigger actions beyond the intended scope.

Failure mechanism: The application trusts a request, session, role, or object reference without verifying that the caller is entitled to that exact resource or operation.

Impact: Data exposure, unauthorised state change, cross-tenant access, and, in some systems, a path to broader compromise through administrative or workflow abuse.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP ASVS, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV8 — AuthorizationCWE-863 is an authorization failure at object and function level.
Recommendation — Verify every sensitive request is authorized against the specific resource and action.
NIST SP 800-53 Rev 5AC-3 — Access EnforcementThis weakness is the failure to enforce permitted access on each operation.
Recommendation — Enforce access decisions at the point of request for every protected object and action.
CIS Controls v8CIS-6 — Access Control ManagementIncorrect authorisation reflects weak access control enforcement and review.
Recommendation — Review and validate access paths so users can only perform approved actions.

Practitioner Guidance

Why practitioners should care: CWE-863 is rarely fixed by one generic control because the real problem is inconsistent enforcement. Teams should treat it as a design-and-testing issue, not just a code-review comment, and ensure that every sensitive action has a clear authorisation decision tied to the specific object and context.

What to watch for: Endpoints that accept direct object references, functions that behave differently across UI and API paths, and code that assumes role membership alone is enough to authorise access. Those are the places where missing checks most often hide.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org