Skip to content
BackEsc
Connect AISign inSign up free

ORM Leak · passage 1 of 12

ORM Leak

Text · ORM Leak/README.md

For testing systems you own or are authorised to test, and for defending them. Nothing here is run by this page.

Connect AI

Open this passage on GitHub

> An ORM leak vulnerability occurs when sensitive information, such as database structure or user data, is unintentionally exposed due to improper handling of ORM queries. This can happen if the application returns raw error messages, debug information, or allows attackers to manipulate queries in ways that reveal underlying data.

Source: ORM Leak/README.md in PayloadsAllTheThings. From PayloadsAllTheThings by Swissky and contributors. MIT License, Copyright (c) 2019 Swissky.

Every one of the 12 is a mark on the map. Named now: 1 to 12, reading order first.

  1. ORM Leak§ 1text · README.md
  2. Django (Python)§ 21 code block · README.md
  3. Query filter§ 31 code block · README.md
  4. Relational Filtering§ 4text · README.md
  5. One-to-One§ 51 code block · README.md
  6. Many-to-Many§ 61 code block · README.md
  7. Error-based leaking - ReDOS§ 71 code block · README.md
  8. Prisma (Node.JS)§ 83 code blocks · README.md
  9. One-to-One§ 9text · README.md
  10. Many-to-Many§ 101 code block · README.md
  11. Ransack (Ruby)§ 11text · README.md
  12. CVE§ 12text · README.md

Zoom in on the map and the dots under the middle of it are named where they are.

Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Source: PayloadsAllTheThings by Swissky and contributors, MIT License. For authorised testing only.

CyberSIXTSignal over noise
Sign inSign up free

Updated