Access Control Vulnerability
Pronunciation: AK-sehs kun-TROHL vul-nur-uh-BIH-lih-tee
Definition
An access control vulnerability lets a user perform actions or reach data that the system should deny to that identity. Defenses against Access Control Vulnerability combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
An access control vulnerability lets a user perform actions or reach data that the system should deny to that identity. Defenses against Access Control Vulnerability combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Mechanism and operation
An access control vulnerability exists when an application fails to enforce who may view, change, delete, approve, or execute a protected resource. The flaw may affect user interfaces, APIs, administrative functions, files, wallets, or individual business objects. Common causes include missing server-side checks, trusting client-supplied roles, predictable identifiers, excessive permissions, and inconsistent authorization across endpoints. Attackers may exploit the weakness by changing a request parameter, calling a hidden route, or reusing another user’s object identifier. Prevention requires centralized authorization rules, deny-by-default behavior, least privilege, object-level checks, and tests covering every protected action. Logs should record denied and successful sensitive operations so teams can investigate misuse and detect privilege escalation.
Practical payment example
A user alters an invoice identifier in an API path and gains access to another merchant’s record, exposing an authorization defect.
Operational checks
Access control must be enforced for every request on the server, regardless of what the interface displays or hides. Assessment of Access Control Vulnerability should trace access control vulnerability lets a user perform actions or reach data that the system should deny to that identity from prerequisite and entry point through observable impact on the affected service.
Distinctions and limits
A theoretical weakness or scanner result involving access control vulnerability lets a user should not be reported as exploitation without corroborating logs, transactions, or configuration evidence. Prevention, detection, containment, and recovery for the Access Control weakness should be tested against the architecture associated with access control vulnerability lets a user.
Related reading
Related definitions: vulnerability, authorization.
Example
A user alters an invoice identifier in an API path and gains access to another merchant’s record, exposing an authorization defect.
Comparison
A theoretical weakness or scanner result involving access control vulnerability lets a user should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Key Takeaway
Access control must be enforced for every request on the server, regardless of what the interface displays or hides.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)