Weakness · High
CWE-425: Direct Request ('Forced Browsing')
What it is
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
- Severity (our rating)
- High
- Likelihood of exploit
- Not rated by MITRE
- Introduced during
- Implementation, Operation
- Exploited in the wild
- 2 known exploited CVEs
In more detail
Web applications susceptible to direct request attacks often make the false assumption that such resources can only be reached through a given navigation path and so only apply authorization at certain points in the path.
What an attacker can do
- Read Application Data (Confidentiality, Integrity, Availability, Access Control)
- Modify Application Data (Confidentiality, Integrity, Availability, Access Control)
- Execute Unauthorized Code or Commands (Confidentiality, Integrity, Availability, Access Control)
- Gain Privileges or Assume Identity (Confidentiality, Integrity, Availability, Access Control)
How to prevent it
Architecture and Design
- Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
- Consider using MVC based frameworks such as Struts.
Exploited in the wild: 2 CVEs
Vulnerabilities caused by CWE-425 that attackers have used, from CISA's Known Exploited Vulnerabilities catalog, newest first.
H2 Security
Found it in your code?
We review where it appears, fix it with your team, and check it was not already used against you.
Talk to our teamT Academy
Stop writing it in the first place
Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.
Start freeSource: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.