Back to Vulnerabilities
Testing methodology

How APVISO Tests for IDOR

IDOR vulnerabilities allow one user to access another user's records by changing object identifiers such as IDs, UUIDs, slugs, or document keys.

Common Locations

  • REST resource IDs
  • GraphQL object queries
  • File downloads
  • Invoices and reports
  • Tenant-scoped admin pages

APVISO Test Vectors

  • Identifier swapping
  • Sequential ID checks
  • Cross-account requests
  • Role downgrade comparisons

Evidence Collected

  • Two-account proof
  • Object identifier
  • Unauthorized response sample
  • Authorization check recommendation

Remediation Themes

  • Enforce server-side ownership checks
  • Test with multiple roles
  • Avoid client-trusted tenant IDs
  • Centralize object authorization

Methodology

IDOR testing requires application context. APVISO looks for object identifiers in URLs, API bodies, GraphQL queries, download links, and hidden fields, then tests whether changing those identifiers crosses an authorization boundary.

The most valuable tests use two or more accounts. The scanner agent compares access across tenants, users, and roles while the lead agent evaluates whether the behavior is true unauthorized access or expected sharing. This helps reduce noise and keeps findings tied to business impact.

Confirmed IDOR findings show the object, the unauthorized request, and the expected access rule. Remediation guidance focuses on centralized server-side authorization, tenant scoping, and automated regression tests so the issue does not reappear in the next release.

Frequently Asked Questions

Does APVISO need multiple test accounts to find IDOR?

Multiple scoped accounts improve coverage because APVISO can compare what each role and tenant should be able to access.

Are UUIDs enough to prevent IDOR?

No. Unpredictable IDs reduce guessing but do not replace server-side authorization checks for each object access.

Related Compliance Guides

Related Terms

Related Integration Workflows

Test for Insecure Direct Object Reference with APVISO

Run autonomous AI pentests that validate exploitability and produce developer-ready evidence.

Contact sales