Security Plugins Hub

Bring your software development workflows to security


Doctrine injection

Signals & Triggers

On Doctrine query execution
If user input alters DQL query structure


  • Block the HTTP request Block the HTTP request
  • Log request stack trace Log request stack trace
  • Log the malicious request Log the malicious request
  • Report an incident Report an incident


  • Send an email to all team members Send an email to all team members
  • Send a Slack notification. Send a Slack notification.
  • POST to your Webhook. POST to your Webhook.
  • Send to New Relic Insights. Send to New Relic Insights.
  • Create an incident on PagerDuty (coming soon) Create an incident on PagerDuty (coming soon)


Doctrine is the most popular PHP Object Relational Mapper (ORM). It comes with its own query language specification, called Doctrine Query Language (DQL).

In essence, DQL provides powerful querying capabilities over your object model. Imagine all your objects lying around in some storage (like an object database). When writing DQL queries, think about querying that storage to pick a certain subset of your objects.

At runtime, DQL is validated and converted to regular SQL. Injections can happen at the DQL level.

Let’s look at the following DQL query:

$query = $em->getRepository('AppBundle:User')->createQueryBuilder('p')
   ->where("p.username = '".$request->request->get('username')."'")
   ->where("p.password = '".$request->request->get('password')."'")

The p.username and p.password fields are sourced from the user inputs. Looking at the DQL query at runtime, Sqreen can detect vulnerable HTTP requests without false positive by using the full context of the app.

Advanced details

When the application starts, the Sqreen PHP library hooks the main Doctrine query builder methods. It catches queries just about to be executed.

Next, on every database request, Sqreen parses the DQL query, just before it is executed. It checks for non-sanitized operators - OR, AND, UNION, … - coming from the user inputs, altering the original query structure and enabling an attacker to derive its original purpose.

No traffic redirection is performed, the analysis of the query happens locally only on your application, relying on Sqreen’s dynamic instrumentation of Doctrine.

By being in-app and running just before the query is converted to SQL we can guarantee a 100% non-false positive detection and protection for Doctrine injections.

Language support

  • PHP

Data collected by Sqreen


No sensitive data collected

On attack
  • DQL query
  • Request payload
  • Attacker IP
  • Attacker account (Sqreen SDK)
  • Stack trace

Built for developers and modern apps

Get up and running in minutes just by installing our lightweight library. Enable plugins in just a couple of clicks.

  • Ruby
  • Node.js
  • PHP
  • Python
  • Java
  • Go
  • .net
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9

$ echo "gem 'sqreen'" >> Gemfile

$ bundle install

$ echo "token: your token" > config/sqreen.yml

$ npm install --save sqreen

$ echo '{ "token": "your token" }' > sqreen.json

$ curl -s > && bash your token

$ pip install sqreen

$ echo -e "[sqreen]\ntoken: your token" > sqreen.ini

$ curl -o sqreen.jar

Request your beta access for the Go agent Request beta
Get notified when the .net agent releases Notify me

Build amazing products. Keep them safe.

5 min installation · Try all features for 14 days · No credit card required Sign up Request demo