Skip to content
TrustedSkillsbeta
Back to all skills

Idor Vulnerability Testing

Listed
sickn33·vlatest·security·MIT

Identifies potential IDOR vulnerabilities by systematically probing resource access based on predictable identifiers.

Repository

Install on your platform

This skill no longer installs under the name idor-vulnerability-testing. sickn33/agentic-awesome-skills has no skill named "idor-vulnerability-testing" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-11-02. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

sickn33

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 7727 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as sickn33/antigravity-awesome-skills.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to systematically identify Insecure Direct Object Reference (IDOR) vulnerabilities within web applications. It automates the process of manipulating object identifiers in URLs or request parameters to verify if unauthorized users can access resources belonging to other accounts.

When to use it

  • During security assessments of APIs that rely on user IDs, order numbers, or transaction codes for resource access.
  • When auditing authentication bypass risks where session tokens or primary keys are exposed in query strings.
  • To validate whether an application properly enforces authorization checks alongside its authentication mechanisms.
  • As part of a broader penetration testing workflow to uncover data leakage before production deployment.

Key capabilities

  • Automatically generates test requests with modified object identifiers (e.g., changing user_id=101 to user_id=102).
  • Compares responses to detect if the application returns sensitive data for non-owned resources.
  • Reports findings on potential unauthorized access vectors across various HTTP methods and endpoints.

Example prompts

  • "Test this API endpoint for IDOR vulnerabilities by swapping user IDs in the request parameters."
  • "Scan the provided login page URL for insecure direct object references that could expose private profiles."
  • "Simulate an attack where I modify order numbers to see if I can view other customers' purchase history."

Tips & gotchas

Ensure you have explicit authorization before testing any live environment, as IDOR scans may trigger false positives or unintended access attempts. This skill is most effective when combined with manual verification of business logic flaws that automated tools might miss.