Skip to content

Interview question · Application & API Security

We use an ORM everywhere. Explain how SQL injection still happens, including second-order injection, and how you would review for it.

An ORM parameterises the queries it builds. It cannot protect the queries you build around it, or the data you trusted because it came from your own database.

hardNewPreparation tags: Amazon, Microsoft, SalesforceUpdated Nov 2026

An ORM parameterises the queries it builds. It cannot protect the queries you build around it, or the data you trusted because it came from your own database.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 6 follow-ups like an interviewer would

A Django app uses the ORM everywhere except a few reporting queries, and a nightly job builds SQL from stored report names.

  1. Do ORMs prevent SQL injection?
  2. How would you find escape hatches?
  3. What is second-order injection?
  4. How do you fix the nightly job?
  5. How do you prevent recurrence?
  6. How would you secure the app?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.