Forced Browsing

Forced browsing is the practice of reaching a resource by guessing or constructing its URL directly, rather than following any link the application actually provides to get there. Real-world instances span a wide range: bypassing a blanket 403 by spoofing an X-Forwarded-For header the access-control rule trusted too much, guessing a deep-link path prefix on a mobile app that skips a check the main flow enforces, stumbling onto a public PDF or vendor/composer directory listing that was never meant to be browsable, or finding a bug bounty program's scope details before the program had officially launched simply by guessing the page existed.

• Reverse-proxied apps with header-based access control
• Mobile apps with deep-link routing
• PHP / Composer-using sites
• WordPress sites with default uploads directory

• Probe with X-Forwarded-For: 127.0.0.1
• Add ../ to deep-link path
• Probe vendor/composer/installed.json
• Direct-URL access to /uploads/ /backups/ /pdfs/ paths

• GET / X-Forwarded-For: 127.0.0.1
• /vendor/composer/installed.json
• /.git/config
• /uploads/<filename>
• deep-link://target/path/../sensitive

Combine 403-bypass header and method manipulation with a broad probe of conventional sensitive-file and directory paths, since forced browsing is fundamentally about reaching content through means other than following the application's own links, whether that's guessing a path directly or defeating a restriction on one already discovered.

Tip: Testing tools that run these checks in parallel across every discovered endpoint can cut the time required substantially compared to fully manual testing, as long as they confirm findings with more than one signal to keep the false-positive rate down.

Existing module's content-similarity guard required.

Manual Testing Methodology

Here is a systematic approach to identifying Forced Browsing vulnerabilities in a target application.

Before testing, map all input vectors that could be affected. Identify parameters, headers, cookies, and request bodies that interact with the vulnerable component. A proxy such as Burp Suite or OWASP ZAP, paired with normal browsing of the target, is usually enough to build this list.

Send a legitimate request and record the normal response: status code, content length, response time, and any identifying tokens. This baseline matters because it's what you'll compare later responses against once payloads are involved.

Inject test payloads into each identified input vector one at a time. Start with benign detection payloads before escalating to anything that could actually trigger the vulnerability. For Forced Browsing specifically, authenticate as a low-privilege test account, then substitute identifiers belonging to another account (sequential IDs, UUIDs harvested from other responses) into every request, and separately try reaching privileged endpoints/actions directly by URL or method regardless of what the UI exposes to that role.

Compare the response against your baseline, looking specifically for a 200 response containing another user's data, or a privileged action completing successfully, when the authenticated user should have received a 401/403 — compare against the expected-denial baseline for that same request from the same account.

Once a potential vulnerability is detected, confirm it with at least a few independent test cases to rule out coincidence. Document the exact request and response as proof. For Forced Browsing, a confirmed finding typically means showing that attacker-controlled input changes the application's behavior in a way that matters for security, not just that a payload was reflected somewhere harmless.

Real-World Impact

Broken access control and IDOR let attackers access or modify resources belonging to other users simply by changing an identifier, or by reaching an endpoint that should have required a higher privilege level. It's one of the most commonly reported vulnerability classes precisely because the underlying mistake is conceptually simple, yet easy to overlook in authorization logic that only checks whether a user is logged in, not whether they're entitled to the specific resource or action being requested.

Real-world exploitation ranges from reading other users' private messages, files, or financial records, to modifying account settings, to reaching admin-only functionality by requesting it directly regardless of what the UI shows. In multi-tenant applications, it can mean cross-tenant data access entirely. The severity scales directly with how sensitive the exposed resource or action is.

This bug class shows up in virtually every kind of application, from social platforms to banking APIs to healthcare systems, which makes it one of the more consistently valuable checks to run regardless of what the target actually does — and one of the hardest for an automated scanner to catch reliably, since confirming it requires understanding what a specific user should and shouldn't be able to reach.

Prevention and Secure Coding

Preventing Forced Browsing takes a defense-in-depth approach — no single control below is sufficient alone, but together they close off both the primary path and the most common bypasses.

Object-level authorization on every request. Verify the authenticated user actually owns or is entitled to the specific resource identified in the request — on every endpoint that accepts an identifier, not just the ones that seemed sensitive during development.

Centralize the authorization logic. Implement authorization checks in one shared layer or middleware instead of re-implementing them per endpoint; re-implementation is exactly where individual endpoints get missed.

Default-deny. Require an explicit permission grant for each action a role can take, rather than granting broad access and trying to enumerate exceptions.

Indirect references where feasible. Opaque, per-user tokens in place of sequential database IDs make horizontal enumeration harder, though this is a hardening measure, not a substitute for the authorization check itself.

Test authorization from the attacker's seat, not the developer's. Authenticate as a low-privilege user and attempt every action a higher-privilege or different-tenant user could take — the UI hiding a button is not an authorization control.