Security weaknessCWE Top 25 · #19
CWE-284 Broken access control
People can reach pages, data or actions on your site that should be off limits to them.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-284?
Improper Access Control: The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Business impact
What CWE-284 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Other
Effects that depend on context
The impact depends on where the weakness sits in your code and what it can reach.
- Gain Privileges or Assume Identity
In plain English
What Broken access control means for your business
- 540+projects delivered
- 9+years in business
- 23+certified experts
A senior engineer replies within one business day.
Access control is the set of rules that decides who can see or do what. A customer can view their own orders. A staff member can edit products. Only an owner can change billing. Improper access control means those rules are missing, incomplete or enforced in the wrong place, so someone reaches a resource they were never meant to. It is a broad category that covers many more specific permission mistakes.
The business impact depends on what is left open. It may be a single report, or it may be your whole admin area. Attackers who get past access rules can read customer data, change content or prices, create accounts and hide what they did. Because these flaws come from missing logic instead of a coding typo, automated scanners often miss them. You find them by testing each role against each feature.
Where it shows up
- Admin or staff pages that are hidden from the menu but still load for anyone who knows or guesses the address.
- REST API routes and WordPress AJAX actions that check a user is logged in but never check the user’s role or capability.
- Cloud storage buckets, backup folders and export files left publicly readable, so invoices, uploads or database copies can be downloaded without signing in.
- Multi-user stores and SaaS apps where buttons are hidden for lower roles in the interface, yet the server still accepts the action when requested directly.
Free security check
Is CWE-284 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-284
Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Also known as: Authorization
Fix it
How to fix Broken access control
Practical steps in priority order. Share them with your developer or agency.
Deny access by default
Start from no access and grant permissions explicitly. Every route, API endpoint and file location should require a rule that allows it, so anything new or forgotten stays closed instead of open.
Enforce every check on the server
Hiding a link or button is not a control. Verify the user’s identity, role and ownership of the record in server code on each request, including API calls and background actions.
Centralize authorization logic
Put permission checks in one shared layer, such as middleware, policies or capability checks, instead of repeating them in each controller. One tested mechanism is easier to audit than hundreds of scattered conditions.
Apply least privilege to roles
Give each role, API key and service account only the access its job needs. Review roles when staff or vendors change, and remove unused accounts, plugins and integrations that still hold permissions.
Test and log access decisions
Write automated tests that try each sensitive action as every role, including logged-out users, and expect a refusal. Log denied requests and alert on repeated failures so probing is noticed early.
Signs you may be affected
- Logged-out visitors or low-level accounts can open admin screens by typing the address directly.
- Content, prices or settings change and your logs show no authorized staff member made the edit.
- Private files, exports or backups show up in search engine results or open without a login.
Questions to ask your developer
- Are permissions checked on the server for every admin page and API endpoint?
- Which roles exist on our site, and what can each one actually do?
- Are any storage buckets, backups or export files reachable without logging in?
Prevention
What MITRE recommends, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Architecture and Design
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces.
Detection and evidence
How CWE-284 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
Real vulnerabilities it caused
- CVE-2023-26463Chain: IPSec VPN product uses the same variable for multiple purposes in the same function (CWE-1109), leading to incorrect access control (CWE-284) and expired pointer dereference (CWE-825)
- CVE-2022-24985A form hosting website only checks the session authentication status for a single form, making it possible to bypass authentication when there are multiple forms
- CVE-2022-29238Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not prevent direct requests to files in those directories.
- CVE-2022-23607Python-based HTTP library did not scope cookies to a particular domain such that "supercookies" could be sent to any domain on redirect
- CVE-2021-21972Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as.
- CVE-2021-37415IT management product does not perform authentication for some REST API requests, as exploited in the wild per CISA KEV.
How we fix it
From finding to fixed: how Codefreex closes CWE-284
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
FAQ
CWE-284: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
How serious is broken access control?
It can be very serious, because the damage matches whatever is left unprotected. A missing check on a minor page is a small problem. A missing check on user management, orders or payment settings can expose customer data or hand over control of the site. It also tends to be quiet: actions look like normal use, so abuse can go unnoticed.
How do I prevent access control flaws?
Design permissions before you build features. List your roles, decide what each may do, and enforce those decisions in one server-side layer that denies by default. Test every sensitive action as each role. Repeat the review whenever you add a plugin, an integration or a new endpoint, because new code is where gaps often appear.
What is the difference between authentication and access control?
Authentication confirms who someone is, usually through a login. Access control decides what that person may do once you know who they are. A site can have a strong login and still have broken access control if, after signing in, any user can reach other people’s data or admin functions. You need both working together.
What is CWE-284?
CWE-284, “Improper Access Control”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How serious is CWE-284?
It can affect other, with impacts such as varies by context, gain privileges or assume identity. It ranks number 19 on the 2025 CWE Top 25 Most Dangerous Software Weaknesses. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-284?
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software. Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when.
Can Codefreex check my site for CWE-284?
Yes. A senior engineer reviews your site, store or app for CWE-284 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Free security check
Find out if CWE-284 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.