appsec.fyi

Insecure Direct Object Reference (IDOR) Resources

Post Share

A curated AppSec resource library covering XSS, SQLi, SSRF, IDOR, RCE, XXE, OSINT, and more.

Insecure Direct Object Reference (IDOR)

Insecure Direct Object Reference (IDOR) is a vulnerability that arises when attackers can access or modify objects by manipulating identifiers used in a web application's URLs or parameters. It occurs due to missing access control checks, which fail to verify whether a user should be allowed to access specific data.

IDOR vulnerabilities are among the most common and impactful bugs found in bug bounty programs. They typically appear in API endpoints that reference database objects by predictable IDs — user profiles, invoices, messages, or files. An attacker simply changes an ID parameter (e.g., /api/users/1234 to /api/users/1235) to access another user's data. The impact ranges from information disclosure to full account takeover, depending on the affected endpoint.

Common patterns include sequential integer IDs in REST APIs, UUID leakage through other endpoints, and GraphQL queries that expose object references without authorization checks. Prevention requires server-side access control on every request — never relying on obscurity of identifiers alone.

This page collects writeups, tutorials, and tools for finding and exploiting IDOR vulnerabilities, from basic parameter tampering to advanced techniques like BOLA (Broken Object Level Authorization) in modern APIs.

From OWASP

Why IDOR outlives every framework that was supposed to kill it

IDOR is the least sophisticated bug on this site and one of the most frequently paid. There is no payload, no encoding trick, no parser edge case. You change a number in a request and the application hands you somebody else's data. The reason it persists is that nothing in a web framework stops it. Frameworks solved SQL injection with parameterized queries and XSS with automatic output encoding, because both are syntax problems the framework can see. Authorization is a business question — whether this user should see this record — and the framework has no idea what the answer is.

That is also why IDOR resists scanners. A scanner can tell that /api/invoice/1041 returned 200, but not that invoice 1041 belongs to a different tenant. Finding these bugs means holding two authenticated sessions at once and replaying one account's requests with the other's credentials. Most of the substantial writeups collected here are built on exactly that setup, and the interesting part is rarely the discovery — it is working out which identifiers in a large API actually map to sensitive objects.

The failure modes worth knowing: sequential integers are the obvious case, but UUIDs only help if they are unguessable and still checked, and plenty of applications treat an opaque identifier as authorization in itself. Look for IDs echoed in export jobs, webhook payloads, PDF generators and notification emails, where the object is fetched by a background worker that never sees the requesting user. Look at second-order flows: an endpoint that correctly rejects a foreign ID on read may accept it on update, or on the "duplicate this record" action nobody thought of as a read.

Mass assignment sits next door and is often mistaken for IDOR. If you can add "role":"admin" or "account_id":7 to a JSON body and the ORM binds it, the object reference was never the problem. Several entries below cover both, and it is worth reading them together — they fail for the same underlying reason, which is that the server trusted the shape of the request.

Start here: the IDOR learning pathAn ordered route through this library — orientation, then methodology, then research. Read the IDOR guideA long-form, source-cited deep dive synthesized from every resource below. The comprehensive IDOR guide on chs.usA hand-written, in-depth practitioner guide — attacks, testing, and prevention.
Date Added Link Excerpt
2026-11-20 NEW 2026How I Find IDOR Vulnerabilities: My Complete Bug Bounty Hunting Methodology beginner AuthZ Bug BountyThis article outlines a bug bounty hunter's methodology for finding Insecure Direct Object Reference (IDOR) vulnerabilities. IDORs occur when an application exposes a direct reference to an internal implementation object, such as a file, directory, or database key, without sufficient access controls. The author focuses on identifying these flaws as a key area of interest in their bug bounty hunting pursuits. → samadhanshimple.medium.com
2026-11-20 NEW 2026How an GraphQL IDOR leaked AI conversation History and Got me $500 bounty intermediate AI API Sec Bug Bounty GraphQLA security researcher discovered an Insecure Direct Object Reference (IDOR) vulnerability in a GraphQL API that led to the leakage of AI conversation history. This flaw allowed unauthorized access to user chat logs. The researcher successfully reported the vulnerability, earning a $500 bounty for their efforts in identifying and disclosing this security issue.
2026-11-20 NEW 2026ProjectSend: clients can read/revoke staff public links (IDOR) news 6 min read AuthZWriteup of GHSA-g9g5-qxp7-f7v2 detailing an Insecure Direct Object Reference (IDOR) vulnerability in ProjectSend versions 2.5.0 through 2.7.1. This flaw allowed clients to view and revoke public links created by staff on client-uploaded files, bypassing intended authorization checks. The issue stems from the file editor and revocation endpoints failing to properly authorize link management based on the creator. ProjectSend 2.8.0 and later versions address this by enforcing creator-based link permissions.
2026-11-20 NEW 2026WriteFreely cross-user post pin/unpin IDOR intermediate AuthZWriteFreely advisory details a cross-user post pin/unpin IDOR vulnerability. This flaw allows any logged-in user on a multi-user instance to manipulate another user's blog navigation by pinning or unpinning their published posts. Attackers can add or remove links from a blog's navigation menu and hide individual posts from main pages and feeds. The vulnerability, reported by 5ud0 (Tarmo Technologies), is rated moderate and affects display only, not post content or other blog settings.
2026-11-20 NEW 2026Cross-region IDOR in Head Start TTADP: read and write another region's data news 4 min read API Sec AuthZWriteup detailing a cross-region Insecure Direct Object Reference (IDOR) vulnerability in the Head Start TTADP application. This vulnerability, categorized under CWE-639 and CWE-862, allowed authenticated users with minimal privileges to read another region's communication logs or write objectives to another region's activity reports. The flaw stemmed from authorization checks being performed against a user-supplied region rather than the actual region of the target data. The issue was fixed in PR #4124, deployed on 2026-11-10, and documented under advisories GHSA-9r9x-g862-525c and GHSA-q859-79hf-rpr3.
2026-11-20 NEW 2026Daptin: Broken Access Control (IDOR) in generic YJS collaboration endpoint news 5 min read API Sec AuthZLibrary with a broken access control vulnerability (IDOR) in its generic YJS collaboration endpoint (`GET /yjs/:documentName`). Any authenticated user can read and write the content of any `file.*`-typed column on any row of any table, including admin-only tables like `calendar`, by supplying a valid `typename.referenceId.columnName` triple, bypassing existing authorization checks. The vulnerability stems from the generic endpoint's lack of per-resource authorization.
2026-11-20 NEW 2026WriteFreely cross-user IDOR: change another user's blog settings news AuthZWriteFreely vulnerability GHSA-7mmq-gh5f-97p3 details a cross-user Insecure Direct Object Reference (IDOR) allowing any logged-in user to modify settings for blogs they do not own. Attackers could change a target blog's title, description, visibility, custom CSS, and other administrative parameters, impacting multi-user instances. The vulnerability is rated high severity as it requires only an ordinary account and the target blog's address.
2026-11-19 NEW 2026Attendize EventOrdersController authorization bypass intermediate AuthZWriteup of GHSA-4558-rxcv-3h92 in Attendize v2.8.0 detailing an authorization bypass in `EventOrdersController::postCancelOrder()`. This vulnerability permits authenticated organizers to cancel attendees from unrelated events by supplying foreign attendee IDs, leading to ticket invalidation for any event on the installation. The issue stems from `Attendee::findFromSelection()` loading attendee IDs unfiltered.
2026-11-19 NEW 2026Fleet authorization bypass in deprecated endpoint news AuthZFleet versions prior to 4.92.0 have a critical authorization bypass vulnerability. This flaw in a deprecated endpoint allows unauthorized access to fleet data. Attackers can exploit this to view sensitive information. Users are strongly advised to upgrade to Fleet 4.92.0 or later to patch this vulnerability and secure their data.
2026-11-19 NEW 2026django-filer missing per-object authorization news 2 min read AuthZAdvisory for GHSA-vf85-8ff2-3r9w details an authorization bypass in `django-filer` versions <= 3.4.4 when per-folder permissions are enabled. The "Delete files and/or folders" admin action fails to enforce per-folder edit permissions, allowing staff users with read-only folder scope and global delete permissions to remove files and folders. This vulnerability is not a read-confidentiality issue but an integrity and edit-control gap, fixed in version 3.5.0.
2026-11-19 NEW 2026How I Found IDOR, SQLi and XSS on NASA intermediate AuthZ Bug Bounty Recon SQLi XSSThe author details finding three security vulnerabilities on a NASA subdomain: Insecure Direct Object Reference (IDOR), SQL Injection (SQLi), and Cross-Site Scripting (XSS). The write-up aims to share the process of discovering these issues. → infosecwriteups.com
2026-11-19 NEW 2026Attendize cross-account authorization bypass news AuthZWriteup of GHSA-f6xp-vhj9-h63x and CVE-2026-132774 affecting Attendize through 2.8.0. This vulnerability, found in `EventAttendeesController::postMessageAttendees()`, allows authenticated organizers to message attendees of other accounts by providing a foreign `event_id`. Exploiting this enables attackers to send arbitrary emails, facilitating phishing and impersonation attacks by leveraging the cross-account authorization bypass.
2026-11-18 NEW 2026Facebook IDOR: Deleting Any Photo Album (Case Study) intermediate AuthZ Bug BountyA vulnerability on Facebook allowed users to delete any photo album they could view through the Graph API. This IDOR (Insecure Direct Object Reference) flaw occurred because the API lacked a proper ownership check, enabling unauthorized deletion of photo albums. The case study details how this exploit functioned, its potential impact, and the subsequent API fixes implemented by Facebook to address the security gap. → masimshahzad.medium.com
2026-11-18 NEW 2026Habitat IDOR intermediateWriteup of Habitat IDOR (GHSA-2955-456r-p77r, CVE-2026-130859). Versions of Habitat up to 1.7.1 are vulnerable in CreatePostController::addAttachmentsToPost() allowing authenticated users to claim other users' unposted image uploads. Attackers can submit sequential attachmentIds during post creation to attach another user's pending image, making it public and removing it from the original uploader's post.
2026-11-18 NEW 2026wishthis authorization bypass in User::ownsWish intermediate AuthZAdvisory for CVE-2026-130851 details an authorization bypass vulnerability in wishthis version 1.2.3, specifically within the `User::ownsWishlist()` function. This flaw enables authenticated users to manipulate other users' wishes and wishlists by providing sequential `wish_id` and `wishlist_id` values to the relevant API handlers. Attackers can exploit this to edit, add, rename, or delete wishes and wishlists.
2026-11-18 NEW 2026EveryDocs Core authorization bypass intermediate AuthZAdvisory GHSA-fphh-x7fg-5xpm details an authorization bypass in EveryDocs Core before 1.6.1. Exploiting unscoped `Model.find(params[:id])` lookups in multiple controllers allows authenticated users to access, modify, or delete other users' documents, files, folders, tags, and people by enumerating sequential IDs. This vulnerability is also referenced as CVE-2026-130857.
2026-11-18 NEW 2026Pytition IDOR intermediate PythonLibrary Pytition (versions prior to 2.10) exhibits an Insecure Direct Object Reference (IDOR) vulnerability within the `show_signatures` view. This flaw permits authenticated users to delete signatures from any petition by providing foreign signature IDs. Attackers can exploit this by posting sequential signature IDs from their own petition's signatures page, leading to the permanent deletion of signatures from any user-owned petition and triggering confirmation emails to other signers, as documented in GHSA-4r8m-4h9q-v4cj and CVE-2026-130872.
2026-11-17 NEW 2026B3log Solo missing authorization in B3Receiver intermediate AuthZAdvisory for B3log Solo through 4.4.0 detailing a missing authorization vulnerability in B3Receiver.receiveArticle. Visitor accounts can modify any article via the POST `/apis/symphony/article` endpoint by supplying their username as `userB3Key`, allowing overwrites of article title, content, and tags.
2026-11-17 NEW 2026free5GC WebConsole authorization flaw in ChangePasswordInfo intermediate AuthZAn authorization flaw exists in the ChangePasswordInfo component of free5GC WebConsole versions up to 1.4.6. This vulnerability allows unauthorized users to change the passwords of other users. The issue stems from insufficient authorization checks within the password change functionality, enabling potential privilege escalation and account compromise. Users are advised to update to a patched version of free5GC WebConsole to mitigate this security risk.
2026-11-17 NEW 2026phpMyFAQ authorization bypass (critical) intermediate AuthZAdvisory for GHSA-29w5-2rqq-hh6x detailing an authorization bypass in phpMyFAQ versions before 4.1.12 and 4.2.0-RC.2. This vulnerability affects multisite deployments by allowing attackers to overwrite passkeys of other tenants through a shared PHP session store, enabling account takeover via cross-tenant WebAuthn manipulation. Affected versions include 4.1.9, and the exploit leverages the WebAuthn prepare() function to achieve unauthorized access.
2026-11-17 NEW 2026phpMyFAQ authorization bypass (4.2.0 RC) intermediate AuthZThis content describes an authorization bypass vulnerability in phpMyFAQ versions from 4.2.0-alpha up to, but not including, 4.2.0-RC.2. This vulnerability allows unauthorized access to sensitive information or functionalities within the application.
2026-11-17 NEW 2026phpMyFAQ authorization bypass intermediate AuthZWriteup of CVE-2026-130383 in phpMyFAQ, an authorization bypass affecting versions prior to 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2. Authenticated editors can manipulate search index documents by providing an arbitrary solutionId to the /admin/api/faq/update endpoint, potentially allowing category-restricted editors to remove published FAQs, overwrite others, or plant searchable entries after unpublishing. The vulnerability is detailed in GitHub advisories and references specific commits and releases.
2026-11-16 NEW 2026Laravel Temporary Signed URLs: Invalid Signature, Expiry, and IDOR intermediate AuthZThis article, assisted by AI and reviewed against Laravel 13.x documentation, discusses vulnerabilities in Laravel's temporary signed URLs. It covers issues related to invalid signatures, which occur when URL parameters are tampered with or when the signature generation is flawed. The content also addresses expiry problems, where URLs may not be expiring as intended, and Insecure Direct Object References (IDOR) vulnerabilities that can arise from improper validation of signed URLs, potentially allowing unauthorized access to resources.
2026-11-16 NEW 2026Course-tencent-cloud IDOR newsWriteup of CVE-2026-129469 in Course-tencent-cloud, detailing an insecure direct object reference (IDOR) vulnerability. Versions prior to 2.0.2 allow unauthenticated attackers to view other users' refund previews by manipulating the order SN parameter in the `/api/refund/confirm` endpoint. Attackers can generate valid SN values from Sqids-encoded sequential order IDs using the default key, leading to disclosure of sensitive order details.
2026-11-16 NEW 2026Snapchat: Delete anyone's content spotlight remotely. news Bug Bounty GraphQLA high-severity vulnerability in Snapchat's Spotlight feature, an Insecure Direct Object Reference (IDOR), allows remote deletion of any user's content. By intercepting a delete request for one's own Spotlight post and changing the `id` parameter to that of another user's video, attackers can remove content belonging to anyone. This could significantly impact popular creators and influencers. → hackerone.com
2026-11-16 NEW 2026GeoPulse IDOR in GET endpoint intermediate AuthZWriteup detailing an Insecure Direct Object Reference (IDOR) vulnerability in GeoPulse versions 1.5.0 through 2.3.0. The flaw, present in the GET /api/v1/places/geocoding/{id} endpoint, allows authenticated users to access the private location data of other users by enumerating sequential `reverse_geocoding_location` IDs. This enables retrieval of custom place names, city, country, coordinates, and bounding boxes from user history. References include CVE-2026-129467 and advisory links detailing the exploit.
2026-11-15 NEW 2026Ryot 10.5.6 authorization bypass (IDOR) intermediate AuthZVulnerability report detailing an authorization bypass in Ryot versions prior to 10.5.6. The issue allows authenticated users to revoke any user's access links by exploiting an IDOR in the `revokeAccessLink` GraphQL mutation. Attackers can craft requests using access link IDs found in public share URLs, bypassing ownership checks and disrupting shared access.
2026-11-15 NEW 2026OpenMage Magento-LTS IDOR intermediate AuthZOpenMage Magento-LTS versions prior to 20.18.2 and 21.0.0-beta1 are vulnerable to an Insecure Direct Object Reference (IDOR) flaw. This vulnerability allows authenticated users to access or manipulate data they should not have permission to view or alter. The issue affects specific versions of the Magento-LTS project.
2026-11-15 NEW 2026Zr.Admin.NET insecure direct object reference (high) intermediate AuthZWriteup of CVE-2026-129454 in Zr.Admin.NET detailing an insecure direct object reference vulnerability. Versions from commit 85cff6a through eb9228a are affected, allowing authenticated low-privilege users to access others' workflow instances, including sensitive form data and approval records, by enumerating sequential instance IDs via GET /workflow/instance/{instanceId}.
2026-11-15 NEW 2026LearnPress Course Wishlist 4.1.2 IDOR beginner AuthZLibrary containing proof-of-concept exploit code for GHSA-33v5-7wpw-28gp, an Insecure Direct Object Reference (IDOR) vulnerability in LearnPress Course Wishlist Add-on versions prior to 4.1.2. Attackers can manipulate any user's course wishlist via the `render_button` callback by supplying an arbitrary `user_id` parameter through the publicly accessible `load_content_via_ajax` REST route, which requires only a public `wp_rest` nonce. This allows for adding or removing courses and enumerating wishlist contents.
2026-11-15 NEW 2026SurveyKing 1.12.0–1.13.2 authorization bypass in linked survey (IDOR) beginner AuthZVulnerability report detailing CVE-2026-129153, an authorization bypass in SurveyKing versions 1.12.0 through 1.13.2. This flaw in the linked survey feature allows authenticated attackers to manipulate responses in surveys belonging to other users by exploiting the `loadLinkResult` and `updateLinkSurveyAnswer` functions. The bypass occurs due to a failure to verify that the `linkSurveyId` belongs to the caller's project, enabling unauthorized read, rewrite, or creation of survey answers.
2026-11-14 2026OpenEMR 8.5.0 insecure direct object reference news AuthZOpenEMR versions prior to 8.5.0 suffer from an insecure direct object reference (IDOR) vulnerability. This flaw allows unauthorized access to sensitive patient data. The vulnerability can be exploited by manipulating object references, enabling attackers to view, modify, or delete records they should not have access to. Users are strongly advised to update to OpenEMR 8.5.0 or a later version to mitigate this security risk.
2026-11-14 2026Omnispace Agora Project = 26.10.0 IDOR news AuthZAdvisory for Omnispace Agora Project version 26.10.0 detailing an Insecure Direct Object Reference (IDOR) vulnerability. This flaw, present in CtrlMail.php's Ctrl::getCurObj() function, bypasses ownership checks via the reloadMailTypeId parameter, enabling authenticated attackers to read other users' private mail by manipulating the mail identifier.
2026-11-14 2026AcyMailing: subscriber identity not bound to the record (IDOR) news AuthZA vulnerability in the AcyMailing Joomla and WordPress extension allows for Insecure Direct Object Reference (IDOR). This means that subscriber identities are not properly bound to their records. Attackers can exploit this flaw to access or modify subscriber data they are not authorized to see, potentially leading to privacy breaches or data manipulation.
2026-11-14 2026NocoDB 2026.09.0 insecure direct object reference news API Sec AuthZNocoDB versions prior to 2026.09.0 suffer from an insecure direct object reference (IDOR) vulnerability. This flaw allows unauthorized users to access or manipulate data they should not have permission to view or modify. The vulnerability arises from improper access controls, enabling attackers to exploit direct object references within the application. Users are advised to update to version 2026.09.0 or later to remediate this security risk.
2026-11-14 2026Dolibarr 24.0.2 insecure direct object reference (IDOR) news AuthZLibrary for identifying and exploiting Insecure Direct Object References (IDOR) in applications. This advisory details a vulnerability in Dolibarr before 24.0.2, specifically within the REST Documents API for the ticket module. Authenticated API users can bypass company-scope checks to access ticket attachments belonging to other companies, enabling the retrieval of sensitive documents like invoices and contracts by enumerating predictable ticket identifiers.
2026-11-13 2026Candlepin ConsumerResource.setupOwner missing authorization (IDOR) news AuthZWriteup of CVE-2026-111456 affecting Candlepin's ConsumerResource.setupOwner function. This IDOR vulnerability allows a low-privileged attacker with a valid consumer certificate to register a new consumer in a different organization by bypassing authorization checks. Exploitation enables the attacker to view and attach entitlements from the target organization's subscription pools.
2026-11-13 2026Foreman PersonalAccessTokensController IDOR news API Sec AuthZWriteup detailing CVE-2026-86322, an Insecure Direct Object Reference (IDOR) vulnerability in Foreman’s Api::V2::PersonalAccessTokensController. This flaw allows an attacker with create_personal_access_tokens permission to forge Personal Access Tokens for other users by exploiting a missing parent-user authorization check. Successful exploitation can lead to complete account takeover, including administrator accounts, by using the stolen token to authenticate as the victim.
2026-11-13 2026Dokploy before 0.31.1 missing ownership check (IDOR) news AuthZDokploy versions prior to 0.31.1 suffer from an Insecure Direct Object Reference (IDOR) vulnerability due to a missing ownership check. This allows unauthorized users to access or manipulate data that they should not have permission to. The vulnerability stems from inadequate validation of user ownership before granting access to resources.
2026-11-13 2026GraphQL BOLA: one object, many paths, and how to prove the gap intermediate 10 min read API Sec AuthZ GraphQLLibrary for identifying and exploiting GraphQL BOLA vulnerabilities by demonstrating how to map all potential object access paths. It guides users through schema introspection, utilizing tools like Clairvoyance or frontend analysis to uncover all resolvers that can return a specific type, including those mediated by interfaces like `Node`. The library advocates for testing each discovered path with distinct user accounts in a single request, leveraging GraphQL aliases to pinpoint authorization gaps where one resolver correctly checks ownership while others fail to do so, a common issue highlighted in the OWASP API Security Top 10 2023.
2026-11-12 2026The $0 IDOR that was worth more than a $12,500 P1: business logic matters intermediate 1 min read AuthZ Bug BountyWriteup detailing an Insecure Direct Object Reference (IDOR) vulnerability whose business impact ($12,500 P1 award) far exceeded its technical severity. It highlights how understanding developer assumptions, translating technical flaws to financial impact, and chaining access control oversights into workflow takeovers are crucial for discovering high-value bugs beyond automated scanner alerts. The researcher Abhishek Meena emphasizes tying access control flaws directly to executive business impact in bug bounty reports.
2026-11-12 2026Cross-project form-session IDOR in CommCare formplayer (GHSA-qjg7-cgv8-3c43) intermediate 6 min read AuthZLibrary for validating user ownership of form sessions in CommCare's formplayer application. This vulnerability (GHSA-qjg7-cgv8-3c43) allowed users to access, alter, or delete incomplete forms belonging to other users in different project spaces. The fix involved adding a `@ValidateSessionOwner` annotation to routes that resolve sessions by ID, ensuring the caller's identity is checked against the session's owner. This addresses CWE-639 and CWE-862.
2026-11-11 2026Meteroid before 2.2.0 cross-tenant authorization bypass intermediate API Sec AuthZWriteup on Meteroid before 2.2.0 cross-tenant authorization bypass (GHSA-hh33-9q27-w8qf, CVE-2026-125752). The vulnerability lies within the CouponsService UpdateCouponStatus gRPC handler, where UPDATE queries incorrectly filter only on coupon ID, neglecting tenant ID. This allows authenticated users with catalog:manage privileges or a tenant-scoped API key to manipulate coupons belonging to other tenants, including disabling, archiving, or re-enabling them, and retrieving their details.
2026-11-11 2026Microsoft MCP Gateway authorization bypass through user-controlled key news AuthZMicrosoft's MCP Gateway is vulnerable to an authorization bypass flaw, allowing attackers to exploit a user-controlled key. This vulnerability enables unauthorized access to sensitive data and functionalities within the system. The issue stems from improper handling of user-provided keys, which can be manipulated to circumvent existing security measures. Microsoft has acknowledged the vulnerability and is working on a patch. Users are advised to monitor for updates and apply them promptly to mitigate the risk.
2026-11-11 2026BeeS Software Solutions ERP IDOR lets low-privileged users access others' records news AuthZBeeS Software Solutions ERP has a vulnerability allowing low-privileged users to access other users' records due to an Insecure Direct Object Reference (IDOR). This flaw enables unauthorized data retrieval. The issue affects versions prior to September 4, 2026.
2026-11-11 20261Panel-dev CordysCRM before 1.9.6 authorization bypass (IDOR) news AuthZWriteup details CVE-2026-126496, an authorization bypass vulnerability in 1Panel-dev CordysCRM before version 1.9.6. This flaw in CustomerContactController.get allows authenticated users with ordinary contact or customer read permissions to access other users' contacts, including sensitive information like names, phone numbers, and linked customers, by exploiting the lack of organization, owner, or data-scope checks. The vulnerability is exploitable via a GET request to `/account/contact/get/{id}`.
2026-11-11 2026Dolibarr 20.0.0 to 24.0.1 insecure direct object reference news AuthZAdvisory detailing an Insecure Direct Object Reference (IDOR) vulnerability in Dolibarr versions 20.0.0 through 23.0.4 and 24.x before 24.0.2. This flaw, found in `api_expensereports.class.php` payment endpoints, allows authenticated users with expense report read and create privileges to access, create, or modify other users' expense report payments by calling `getAllPayments`, `getPayments`, `addPayment`, or `updatePayment`, thereby manipulating reimbursement status. CVE-2026-125754 is associated with this vulnerability.
2026-11-10 2026langchain4j-aideepin IDOR news AI AuthZAdvisory for GHSA-58f4-85vm-hv79 detailing an Insecure Direct Object Reference (IDOR) vulnerability in langchain4j-aideepin through 3.32.0. The CharacterMessageController allows authenticated users to access other users' message references by exploiting missing owner checks on the knowledge-embedding-ref, memory-embedding-ref, or graph-ref endpoints, potentially exposing knowledge-base chunks, long-term memory text, and knowledge-graph data.
2026-11-10 2026Krayin CRM before 2.2.8 broken object level authorization news API Sec AuthZAdvisory for CVE-2026-125374 in Krayin CRM before 2.2.8 details a broken object level authorization vulnerability within the Lead TagController. This flaw allows authenticated users, even those with restricted data scopes, to attach or detach tags from leads owned by other users outside their authorized scope due to skipped data-scope checks in the attach and detach actions.
2026-11-10 2026How a Guessable Number Exposed Every Meta AI User’s Private Prompts news AI AuthZ Bug BountyA significant vulnerability was discovered in Meta AI, allowing unauthorized access to private user prompts. Security researcher Sandeep Hodkasia identified a flaw where a guessable numerical identifier could expose sensitive user interactions. This means that any individual who could figure out these numbers could potentially view the prompts submitted by other Meta AI users. The extent of the exposure and the implications for user privacy are currently under scrutiny following this critical finding.

Frequently Asked Questions

What is an IDOR vulnerability?
IDOR (Insecure Direct Object Reference) is a type of access control vulnerability where an application exposes internal object references — such as database IDs, filenames, or user identifiers — without proper authorization checks. An attacker can manipulate these references to access other users' data.
How do you find IDOR vulnerabilities?
To find IDORs, look for predictable identifiers in API endpoints, URL parameters, and request bodies. Change IDs (numeric, UUID, or encoded values) to those belonging to other users and observe whether the application returns unauthorized data. Testing with two accounts simultaneously is the most effective approach.
What is the difference between IDOR and BOLA?
BOLA (Broken Object Level Authorization) is the API-specific term for IDOR, used in the OWASP API Security Top 10. Both describe the same core issue: missing authorization checks when accessing objects by reference. BOLA is the preferred term when discussing API security.

Weekly AppSec Digest

Get new resources delivered every Monday.