Missing Function-Level Access Control
Privileged functions check that a user is signed in but not that their role permits the action, so lower-privileged users can call them directly.
| Severity | High |
| CVSS 3.1 | 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 8.6 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-862: Missing Authorization |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application |
| Category | Broken Access Control |
Description
The application exposes functions intended for particular roles, such as administration pages, user management, configuration changes, data exports or approval steps, without checking on the server that the caller's role permits them. The user interface often hides the relevant menu items or buttons from lower-privileged users, but the underlying page or API endpoint still responds to anyone who requests it, and sometimes to unauthenticated requests as well.
A user with a low-privileged account, or an attacker who registers or compromises one, can therefore perform actions reserved for more privileged roles. Depending on the functions exposed, this can include creating accounts, granting themselves administrative rights, changing configuration, reading or exporting all users' data and approving transactions. The impact is greatest where user and role management is exposed, since that gives full control of the application, and where the functions can be reached without authentication.
Common variants include administrative endpoints reachable by standard users, checks applied to one HTTP method but not another on the same route (for example GET protected but PUT or DELETE not), checks enforced on a page but not on the API that page calls, and decisions based on a role or flag sent by the client.
The weakness is identified by recording the requests available to the most privileged role, then replaying them with sessions for lower-privileged roles and with no session at all, and by reviewing client-side code, which often lists administrative API routes that the interface never shows. Burp Suite extensions such as Autorize make this replay systematic. Automated scanners rarely find the issue, because they do not know which roles should reach which functions.
Remediation
Enforce authorisation on the server for every function, based on the role and permissions held in the user's session:
- Deny by default: every route and API operation should require an explicit permission, and any route without one should be refused.
- Implement the checks centrally rather than in each handler, using the framework's own mechanisms, for example Spring Security's
@PreAuthorizeor URL authorisation rules, ASP.NET Core authorisation policies applied with[Authorize(Policy = "...")], or shared middleware in Express and similar frameworks. - Apply the check to every HTTP method on a route and to every API that a page calls, not only to the page itself.
- Never base decisions on hidden interface elements or on role values sent by the client.
- Keep administrative functions under a separate route prefix or host with its own policy, so they can also be restricted at the network edge.
- Maintain a matrix of roles and permitted functions, and turn it into automated tests that run on every release.
Confirm the fix by replaying each privileged request with lower-privileged sessions and with no session, and checking that every one is refused.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.