SQL Injection
SQL injection (SQLi) is the insertion of malicious SQL queries via input data from the client to the application. A successful SQL injection exploit can read sensitive data from the database, modify or delete records, execute administrative operations, and in some cases issue commands to the operating system.
Despite being one of the oldest web vulnerability classes, SQL injection continues to appear in modern applications — particularly in legacy codebases, custom query builders, and applications that construct SQL through string concatenation rather than parameterized queries. Second-order SQLi, where the payload is stored first and executed later in a different context, is especially difficult to detect with automated scanners.
SQLi techniques have evolved well beyond simple UNION SELECT attacks. Blind SQLi uses boolean conditions or time delays to extract data one bit at a time. Error-based injection leverages database error messages to leak information. Out-of-band SQLi exfiltrates data through DNS or HTTP requests initiated by the database. Each database engine — MySQL, PostgreSQL, MSSQL, Oracle, SQLite — has its own syntax quirks and exploitation techniques.
Modern WAFs and prepared statements have reduced the attack surface, but bypasses are regularly discovered through encoding tricks, comment injection, and parser differentials between the WAF and the database.
This page collects SQLi techniques, cheat sheets, bypass methods, and real-world exploitation writeups across all major database platforms.
From OWASP
SQL injection is solved, which is exactly why it still matters
The fix has been known for two decades and is unambiguous: send the query
and the data separately, so that user input can never be parsed as SQL. A
parameterized query is not a mitigation that raises attacker cost — it removes
the class. And yet the bug keeps appearing, because the fix only holds where
it is applied, and real codebases have places it is not: dynamic
ORDER BY and column names, which cannot be parameterized and get
concatenated instead; raw-SQL escape hatches in ORMs; stored procedures that
build strings internally; reporting and search features written against a
different database than the rest of the application.
The techniques below are organized by how much the database tells you. When errors come back, extraction is quick. When they do not but responses differ, boolean-based inference recovers data one condition at a time. When responses are identical, time-based methods use conditional delays, at the cost of a query per bit. Out-of-band methods — making the database resolve a DNS name or open a connection — are fastest of all when the database can reach the network, which is why they appear so often in writeups against otherwise silent targets.
Second-order injection deserves separate attention because it breaks the mental model people bring to testing. Input is stored safely on the way in, then concatenated into a query somewhere else entirely — a scheduled job, an admin view, an export. Nothing happens when you submit the payload, so it looks clean. The writeups here that find these are usually the ones that went looking for where stored values get reused.
On tooling: sqlmap is very good, and leaning on it before you can do the extraction by hand is a mistake that shows up immediately when a target needs a custom tamper script or has a WAF in front of it. Learn the manual path first; the automation makes far more sense afterwards, and so does the substantial body of evasion research collected below.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-11-10 NEW 2026 | MobileHackingLab “Food Store” Lab Writeup intermediate Mobile | This writeup details a MobileHackingLab "Food Store" lab exploring SQL injection vulnerabilities. The lab demonstrates how this typically server-side vulnerability can manifest in a mobile application context. |
| 2026-11-10 NEW 2026 | Group and session filters checked the column name, profile filters didn’t: ClickHouse SQL injection… intermediate Bug Bounty | OpenPanel's analytics filter builder had a SQL injection vulnerability (CVE-2026-88890). While group and session filters correctly validated column names, profile filters did not. This oversight allowed attackers to inject malicious SQL code by exploiting the lack of validation in profile filter parameters, potentially compromising the system. |
| 2026-11-10 NEW 2026 | flowintel migration script SQL injection intermediate Python | A SQL injection vulnerability was identified in a database migration script used by flowintel. This flaw allows unauthorized execution of SQL commands, potentially leading to data breaches or manipulation. The vulnerability has been addressed, and users are advised to update to the latest version of the script to ensure their systems are protected. |
| 2026-11-10 NEW 2026 | Kubeflow Pipelines SQL injection via pagination tokens intermediate AI | Kubeflow Pipelines has a security vulnerability where unvalidated pagination tokens in the API server can lead to SQL injection attacks. This allows attackers to potentially execute arbitrary SQL commands, compromising data integrity and system security. |
| 2026-11-10 NEW 2026 | PortSwigger Lab: Blind SQL Injection with Time Delays intermediate Burp | This PortSwigger Web Security Academy lab focuses on **Blind SQL Injection using time delays**. The challenge is designed for practitioners. The goal is to exploit a blind SQL injection vulnerability where direct output is not provided. Attackers must infer information by observing the application's response time, triggering delays to identify database structures and sensitive data. |
| 2026-11-10 NEW 2026 | Unauthenticated front-end SQL injection (critical) intermediate | An unauthenticated SQL injection vulnerability was discovered in the front-end system. This critical flaw allows attackers to execute arbitrary SQL commands without needing to authenticate. The vulnerability poses a significant security risk, potentially leading to data breaches, unauthorized access, and other malicious activities. |
| 2026-11-09 NEW 2026 | SQL Injection — Pink CTF Web Challenge beginner | This content describes a web challenge from Pink CTF focused on SQL injection. The author begins by accessing a provided link, recognizing the challenge's objective is to exploit SQL vulnerabilities. |
| 2026-11-09 NEW 2026 | PortSwigger Lab: Visible Error-Based SQL Injection intermediate Burp | This PortSwigger lab, rated "Practitioner" difficulty, focuses on **visible error-based SQL injection**. The goal is to exploit a website's susceptibility to SQL injection vulnerabilities where error messages are directly displayed to the user. Successful exploitation likely involves crafting malicious SQL queries that trigger informative database errors, revealing sensitive information or allowing for further manipulation of the database. The lab's purpose is to teach practical techniques for identifying and exploiting this common injection flaw. |
| 2026-11-09 NEW 2026 | OpenEMR before 8.3.0 SQL injection in Fee Sheet (critical) news | OpenEMR versions prior to 8.3.0 are vulnerable to a critical SQL injection flaw in the Fee Sheet functionality. This vulnerability allows attackers to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. Users are strongly advised to upgrade to OpenEMR 8.3.0 or later to patch this security issue. |
| 2026-11-09 NEW 2026 | wpForo Forum time-based SQL injection intermediate | Writeup of CVE-2026-119155, a time-based SQL injection vulnerability in wpForo Forum plugin for WordPress. Affecting versions up to 3.2.2, this flaw arises from insufficient input escaping and query preparation on the 'href[locale]' parameter. Attackers can exploit this by appending malicious SQL queries to extract sensitive data, requiring no authentication or prior interaction beyond visiting a forum page to obtain the necessary nonce. |
| 2026-11-09 NEW 2026 | OpenEMR before 8.3.0 SQL injection in Standard REST API news API Sec | OpenEMR versions prior to 8.3.0 are vulnerable to SQL injection within their Standard REST API. This vulnerability could allow attackers to execute arbitrary SQL commands, potentially compromising sensitive patient data. |
| 2026-11-08 NEW 2026 | One Lab, Three Ways: solving PortSwigger’s SQL Injection Hidden Data lab with Burp intermediate Burp | This content details three distinct methods for solving PortSwigger's "SQL Injection Hidden Data" lab using Burp Suite. The author aims to demonstrate diverse approaches to tackling SQL injection vulnerabilities within this specific lab environment, highlighting the flexibility and power of Burp Suite in identifying and exploiting such flaws. The article likely provides step-by-step instructions and explanations for each of the three solutions presented. |
| 2026-11-08 NEW 2026 | A September SQL-injection fix in Craft missed a second path news 2 min read | Writeup of a bypassed SQL injection fix in Craft CMS, detailing how a GHSA-cphx-cx67-jcqj advisory exploited a vulnerability in Element::findOne() by passing a crafted criteria array that Yii's query builder interpreted as literal SQL. This bypassed a previous fix (GHSA-mjj9-pjh4-r48g) by targeting a different entry point into the same vulnerable sink, highlighting the importance of fixing sinks directly rather than individual call sites to prevent subsequent bypasses. The vulnerability, affecting versions up to 5.11.5, allows blind exploitation and impacts common user actions. |
| 2026-11-08 NEW 2026 | SQL::Abstract before 2.000003 arrayref column SQL injection news | Library for Perl's SQL::Abstract versions prior to 2.000003 that can be exploited for SQL injection. When the `array_datatypes` option is off (the default), the `insert()`, `update()`, and `values()` methods treat arrayref column values literally. The first element of the arrayref is inserted unescaped into the SQL text, with subsequent elements used as bind values. This vulnerability affects applications that use request data as column values without escaping, including through `generate()` and `AUTOLOAD` when `allow_autoload` is enabled. |
| 2026-11-08 NEW 2026 | Wazuh SQLi in WazuhDBBackend._substitute_params leaks agent secrets news 7 min read Secrets | Writeup detailing a SQL injection vulnerability in Wazuh's `WazuhDBBackend._substitute_params` function. This flaw allows authenticated API users with `agent:read` privileges to bypass RBAC restrictions and extract sensitive agent secrets, such as `internal_key`, from `global.db`. Exploitation is achieved through placeholder cross-contamination, leading to a blind boolean oracle on the `total_affected_items` response field, enabling character-by-character data exfiltration. |
| 2026-11-08 NEW 2026 | wpForo Forum generic SQL injection via the data parameter news | Writeup of GHSA-6xr2-4pq6-5xf6, detailing a generic SQL injection vulnerability in wpForo Forum plugin versions up to 3.2.1. This flaw stems from insufficient escaping of the 'data' parameter and inadequate SQL query preparation, enabling unauthenticated attackers to extract sensitive database information. Exploitation is contingent on specific forum field configurations, such as checkbox or multi-choice select fields. |
| 2026-11-08 NEW 2026 | Amelia Pro booking plugin SQL injection news | Writeup of time-based SQL injection in Amelia Pro plugin for WordPress, versions up to 9.9.1. Unauthenticated attackers can exploit insufficient escaping of the 'tag[]' parameter keys to extract sensitive data. This vulnerability arises from bypassing WordPress's wp_magic_quotes and defeating the plugin's Statement::execute placeholder binder through overlapping strtr() substitution keys in EventRepository::getFilteredIds(). |
| 2026-11-07 NEW 2026 | DBHub: MySQL comment interpretation bypasses read-only SQL validation intermediate 3 min read | Library that allows write and DDL statements to be executed even when in read-only mode for MySQL and MariaDB connectors. This bypass occurs because the DBHub SQL parser's handling of single-line comments differs from MySQL and MariaDB's parsing, enabling malicious payloads like `SELECT 1--1;DROP TABLE victim` to execute arbitrary commands, defeating the intended protection for AI agents interacting with databases. → advisories.gitlab.com |
| 2026-11-07 NEW 2026 | NocoDB SQLi via formula date format argument on MySQL intermediate 1 min read | Library update addressing GHSA-2ggp-wwhj-f84q in NocoDB, a SQL injection vulnerability on MySQL. The `DATETIME_FORMAT` formula argument's `format` parameter was not properly escaped, allowing authenticated users with the Creator role to inject malicious SQL via formula fields. This permits arbitrary read access to database tables and potential denial-of-service conditions by crafting expensive queries. The vulnerability only affects MySQL and MariaDB instances with default `sql_mode` settings; PostgreSQL and SQLite are unaffected. The fix involves escaping backslashes within the format string before it's quoted. |
| 2026-11-07 NEW 2026 | One Lab, Three Ways: Solving PortSwigger’s SQL Injection “Hidden Data” Lab with the Browser, Burp… intermediate Burp | This article details three methods for solving PortSwigger's SQL Injection "Hidden Data" lab. The author demonstrates how to exploit the vulnerability using the browser's developer tools, Burp Proxy, and Burp Repeater. All three approaches utilize the same SQL injection payload, highlighting the versatility of different tools in achieving the same outcome. The focus is on the various delivery mechanisms for a single exploit. |
| 2026-11-07 NEW 2026 | ZDI-26-891 SQL injection advisory news | Advisory ZDI-26-891 details a SQL injection vulnerability in Philips Hue Bridge Pro. Network-adjacent attackers can bypass authentication and execute arbitrary code as root by exploiting improper validation within the HTTP service. This flaw affects firmware versions prior to 6.1.2071524030. → zerodayinitiative.com |
| 2026-11-07 NEW 2026 | DutyBound HTB: PostgreSQL stacked-query SQLi to RCE intermediate 2 min read RCE | Writeup of DutyBound HTB, a medium difficulty Linux machine on Hack The Box, detailing its exploitation path from industrial communication protocols and insecure graphical session controls to achieving complete system compromise. The walkthrough highlights chaining misconfigured internal access vectors and loose validation in automated management tooling, including loose input sanitization and exposed legacy protocols, to achieve RCE. |
| 2026-11-06 NEW 2026 | Dromara SkyEye SQL injection via keyword parameter news | A SQL injection vulnerability exists in Dromara SkyEye, specifically in versions up to commit `65d3ddcede701d33ea5416e47c9b656e47d56401`. This vulnerability, identified as CVE-2026-110609, is rated as HIGH severity with a CVSS score of 7.1. It is exploitable via the keyword parameter. → vulncheck.com |
| 2026-11-06 NEW 2026 | SQL-Abstract Perl SQL injection CVEs (oss-security) news 3 min read | Library provides patches and analysis for three CVEs affecting Perl's SQL-Abstract. CVE-2026-121007 allows SQL injection via nested statement where values. CVE-2026-121008 permits cross-site scripting through unescaped SQL text and bind values in the `html` profile. CVE-2026-121009 bypasses injection guards for function names specified with `-func`. Versions prior to 2.000001_04 are vulnerable. |
| 2026-11-06 NEW 2026 | SQL injection in the Trilogy MySQL adapter news 2 min read | Writeup on GHSA-744p-w4gc-m3gh, a critical SQL injection vulnerability in Trilogy, the MySQL client used by GitHub. Affecting all versions up to 2.13.1 with a CVSS score of 9.3, the bug arises from Trilogy's byte-by-byte string escaping, which incorrectly tags output with the input's encoding. This flaw, exploitable with multibyte encodings like GBK, allows bypasses of Rails parameter validation, as demonstrated by a proof of concept using sqlmap. The fix re-encodes strings to the connection's charset before escaping, and parameterized queries entirely avoid the issue. |
| 2026-11-06 NEW 2026 | Unauthenticated SQL injection in YesWiki exposes password hashes news 3 min read | Writeup of CVE-2026-116207, an unauthenticated SQL injection vulnerability in YesWiki affecting versions 4.6.0 up to, but not including, 4.7.0 and alpha versions up to 5.0.0-alpha4. Attackers can exploit this flaw in the Bazar entries search API by injecting backtick characters into search parameters, allowing arbitrary SQL command execution to steal password hashes or cause denial-of-service conditions via commands like SLEEP(). |
| 2026-11-06 NEW 2026 | CSA alert: active exploitation of Metabase SQL injection news 1 min read | Alert concerning active exploitation of Metabase SQL injection vulnerability (CVE-2026-72898). Unauthenticated remote attackers can inject arbitrary SQL, gaining administrator access. This critical vulnerability, with a CVSS score of 10.0, affects numerous Metabase versions. A proof-of-concept exploit is publicly available. Users should immediately update to patched versions and follow post-upgrade security guidance, including revoking sessions and rotating credentials. A temporary workaround involves blocking access to the `/api/session/reset_password` endpoint. |
| 2026-11-06 NEW 2026 | SurrealDB MCP tool identifier statement injection news 1 min read API Sec | Library patch addressing CVE-GHSA-cr79-9p8r-p5wx in SurrealDB's MCP tool identifier validation. The vulnerability allowed statement injection by exploiting a discrepancy between identifier validation and SQL lexing, where escaped backticks in identifiers were not correctly handled. This enabled arbitrary SQL query execution by breaking out of quoted identifiers. Versions 4.0.0 and later are unaffected. |
| 2026-11-06 NEW 2026 | Unauthenticated SQLi in WPGraphQL 2.11.1 news API Sec GraphQL | Advisory for GHSA-4x56-83j8-4m8f details an unauthenticated SQL Injection vulnerability in WPGraphQL versions prior to 2.11.1. This flaw, identified as CVE-2026-40762, arises because the plugin constructs SQL commands using externally influenced input without properly neutralizing special characters. This allows attackers to inject malicious SQL code, altering the intended query and potentially leading to unauthorized data access or manipulation. |
| 2026-11-05 NEW 2026 | Understanding SQL Injection beginner Bug Bounty | SQL injection (SQLi) remains a persistent and common vulnerability, despite its age. This summary stems from a practical learning experience. SQLi occurs when an attacker inserts malicious SQL code into input fields, which can then be executed by the database. This can lead to unauthorized data access, modification, or deletion. Developers must implement proper input validation and parameterized queries to prevent such attacks. The article focuses on understanding and mitigating this prevalent security flaw. |
| 2026-11-05 NEW 2026 | Web Gauntlet ~ CyLab Security Academy CTF Write-up | SQL Injection and Filter Bypass intermediate Bug Bounty | This write-up details a successful approach to the "Web Gauntlet" challenge in the CyLab Security Academy CTF. The solution involved exploiting SQL injection vulnerabilities to bypass filters. The author explains the process of identifying and leveraging these weaknesses to gain access and solve the challenge. |
| 2026-11-04 2026 | Unauthenticated SQL Injection in Simple School Management System 1.0 — staff_delete.php intermediate AuthN | An unauthenticated SQL injection vulnerability has been discovered in the Simple School Management System version 1.0, specifically within the `staff_delete.php` file. This vulnerability, classified as High severity (CVSS 7.5), could allow attackers to compromise the system. The identified CWEs are CWE-89 (SQL Injection) and CWE-862 (Missing Authorization). |
| 2026-11-02 2026 | From SQL Injection to RCE — HTB SQL Injection Skills Assessment intermediate RCE | This content details a user's journey through the Hack The Box (HTB) SQL Injection Skills Assessment. The assessment progresses from basic SQL injection vulnerabilities to achieving Remote Code Execution (RCE). The user shares their experience and learning process in mastering these advanced SQL injection techniques within the HTB platform. |
| 2026-11-02 2026 | Unauthenticated SQL Injection in Code-Projects Simple School Management System 1.0 news | An unauthenticated SQL injection vulnerability (CWE-89) has been discovered in Code-Projects Simple School Management System version 1.0. This means an attacker can exploit the software without needing to log in or provide any credentials. The vulnerability allows for the injection of malicious SQL commands, potentially leading to unauthorized access, modification, or deletion of sensitive data stored within the system. |
| 2026-11-02 2026 | Unauthenticated SQL injection in WPGraphQL 2.11.1 (CVE-2026-40762) news GraphQL | Advisory detailing CVE-2026-40762, an unauthenticated SQL injection vulnerability in WPGraphQL versions prior to 2.11.1. This flaw occurs because the plugin constructs SQL commands using external input without properly neutralizing special SQL syntax elements. This allows attackers to inject malicious SQL code through user-controlled inputs, altering the intended query. |
| 2026-11-01 2026 | SQLi in user authentication module of Futurum Software (INCIBE-CERT) news AuthN | Writeup of CVE-2026-14571, a Blind SQL Injection in Futurum Software's user authentication module, discovered by Diego González Aguín. This critical vulnerability (CVSS v4.0: 9.1) arises from inadequate input validation and sanitization, along with a flawed Web Application Firewall configuration, enabling unauthenticated attackers to execute arbitrary queries and exfiltrate sensitive PII. |
| 2026-11-01 2026 | Tabularis MCP SQL Injection read-only bypass (news brief) news 4 min read AI | Library for Tabularis versions before 0.28.0, addressing CVE-2026-118378, a SQL injection vulnerability in the SQLite driver. A crafted `table_name` passed to the `describe_table` tool allows attackers, including AI agents, to bypass read-only mode and write approval by executing stacked SQL statements, potentially leading to data modification or deletion. This flaw (CWE-89) has a CVSS 4.0 score of 8.5 from VulnCheck. |
| 2026-11-01 2026 | OpenEMR Syndromic Surveillance authenticated error-based SQL injection intermediate 2 min read | Writeup detailing an authenticated error-based SQL injection in OpenEMR's Syndromic Surveillance module, allowing Clinician-level users to extract bcrypt password hashes and reset any user's password. Exploitation involves abusing MySQL's `extractvalue()` function for data exfiltration and stacked queries for account takeover, bypassing inadequate sanitization by `add_escape_custom()`. The vulnerability affects specific OpenEMR versions and has been patched. |
| 2026-11-01 2026 | Tabularis MCP SQL injection read-only bypass (CVE-2026-118378) news AI | Writeup of CVE-2026-118378 in Tabularis before 0.28.0 details an SQL injection vulnerability within the SQLite driver. MCP clients can exploit a crafted `table_name` argument in the `describe_table` tool to execute stacked statements, bypassing read-only mode. Attackers can close the PRAGMA argument and append commands to read, modify, or drop SQLite data, as identified in advisories GHSA-v867-6qx2-gwmg and NVD. |
| 2026-11-01 2026 | CyLab: Secret Box beginner Secrets | This content describes a "CyLab: Secret Box" web exploitation challenge of medium difficulty. The challenge presents a system advertised as perfectly secure, intended to conceal secrets only visible to the user. However, the description hints at a potential vulnerability, posing the question, "Or can...?" The goal is likely to find a way to bypass the advertised security and access the "secrets." |
| 2026-10-31 2026 | Unpacking CVE-2017–8917: A Hands-On Guide to Reproducing and Fixing the Joomla com_fields SQL… intermediate | This article provides a detailed, hands-on guide to reproducing and fixing CVE-2017–8917, a SQL injection vulnerability affecting Joomla's `com_fields` component. The vulnerability allows unauthenticated attackers to extract sensitive data from the database. The author walks through the exploitation process, demonstrating how to trigger the SQL injection and gain access to database information. Crucially, the post also offers a clear explanation of the fix and provides guidance on how to patch affected Joomla installations to prevent exploitation. |
| 2026-10-31 2026 | How I Solved PortSwigger SQLi Labs 1–6 (Part 1 Walkthrough) intermediate | This article details a walkthrough of PortSwigger's SQL injection (SQLi) labs, specifically covering the solutions for labs 1 through 6. The author provides step-by-step guidance on how to exploit common SQL injection vulnerabilities within these exercises, offering practical insights for learning and practicing SQLi techniques. The content focuses on the methodologies and commands used to identify and leverage these flaws in a controlled lab environment, aiming to enhance the reader's understanding of web application security. |
| 2026-10-31 2026 | Deep Dive into Patch Diffing: Analyzing the Code-Level Fix for CVE-2017–8917 in Joomla! advanced | This article details a deep dive into patch diffing, specifically analyzing the code-level fix for CVE-2017–8917 in Joomla!. Patch diffing is a technique used to understand security vulnerabilities by comparing vulnerable code with its patched version. The analysis focuses on how the fix addresses the identified security flaw in Joomla!, providing insights into the methods and processes involved in reverse engineering and code analysis for security purposes. |
| 2026-10-31 2026 | Injection Attacks Through the Ages: From Turing Machines to Prompt Injection beginner AI Talks | Talk from OWASP Foundation detailing the historical evolution of injection attacks, tracing their roots from foundational concepts like Turing machines and classical vulnerabilities such as SQL injection and command injection, to contemporary threats like prompt injection in AI systems, offering historical context and defense strategies for security professionals and developers. |
| 2026-10-31 2026 | My Journey into Server-Side Security: Learning Through PortSwigger Labs beginner | This content describes a personal journey into learning server-side security through PortSwigger Labs. The author likely details their experiences and the knowledge gained from these practical exercises. The focus is on the educational aspect and skill development in the realm of server-side vulnerabilities and their mitigation. |
| 2026-10-31 2026 | Unauthenticated SQLi in a GraphQL API: From Guest to Admin Takeover intermediate API Sec AuthN GraphQL | An unauthenticated SQL injection vulnerability was discovered in a GraphQL API, allowing a guest user to escalate their privileges to an administrator. This severe flaw enabled attackers to bypass authentication and gain full administrative control over the system. The vulnerability highlights the critical need for robust input validation and secure coding practices, even in seemingly well-protected API environments. |
| 2026-10-21 2026 | Unauthenticated SQL injection in GLPI (≤ 11.0.8) intermediate 4 min read | Writeup detailing an unauthenticated SQL injection vulnerability in GLPI versions up to 11.0.8. The vulnerability arises from improper handling of date parameters in `front/planning.php` via the `checkavailability` and `genical` parameters, leading to raw concatenation into SQL queries within `CommonITILTask::genericPopulatePlanning()` and `ProjectTask::populatePlanning()`. Exploitation, particularly in GLPI 11.0.8 and the 12-dev branch, allows an attacker to exfiltrate sensitive data such as password hashes or session identifiers, potentially leading to account takeover. The fix involves using `DB::quoteValue()` to properly escape user-supplied data. |
| 2026-09-24 2026 | Breaking the Superuser Guardrails of managed-PostgreSQL Providers intermediate 17 min read RCE | Analysis of security hardening extensions used by managed PostgreSQL providers, including those from Azure, Aiven, Supabase, PlanetScale, Xata.io, AWS Aurora, Google AlloyDB, and NeonDB, reveals significant vulnerabilities. The research details how these extensions, designed to prevent superuser access and block dangerous functions like `COPY TO/FROM PROGRAM`, can be bypassed. The author discovered 76 vulnerabilities across these extensions, highlighting systemic risks and challenging vendor assumptions about tenant isolation. |
| 2026-09-17 2026 | From Bug to Schema: Exploring Error-Based SQL Injection on an Authenticating Portal intermediate AuthN | This paper details the discovery of an error-based SQL injection vulnerability within a production environment, identified through a Vulnerability Disclosure Program (VDP). The analysis focuses on how the vulnerability was found and exploited. The content emphasizes that this case study is for educational purposes, and all sensitive organizational data has been anonymized. → infosecwriteups.com |
| 2026-09-03 2026 | Over 3 Million WordPress Sites Affected by Migration Plugin Vulnerability news 2 min read | Vulnerability in the All-in-One WP Migration and Backup WordPress plugin, CVE-2026-19949, allows unauthenticated remote code execution. The flaw, a second-order SQL injection, exploits insufficiently escaped user input within the archive restore functionality. Attackers can leverage WordPress trackback functionality to extract a secret key, then use it to import a malicious .wpress archive containing a must-use plugin for RCE. Versions up to 7.109 are affected; version 7.110 patches the issue. → securityweek.com |
Frequently Asked Questions
- What is SQL injection?
- SQL injection is a code injection technique where an attacker inserts malicious SQL statements into input fields or parameters that are incorporated into database queries. Successful exploitation can read, modify, or delete database data, and in some cases execute operating system commands.
- What is the difference between blind and error-based SQLi?
- Error-based SQLi extracts data through database error messages visible in the application response. Blind SQLi works when errors are suppressed — it infers data using boolean conditions (true/false responses) or time delays (e.g., IF condition THEN SLEEP(5)). Blind SQLi is slower but works in more restrictive environments.
- Are prepared statements enough to prevent SQLi?
- Prepared statements (parameterized queries) prevent classic SQLi in most cases. However, they cannot parameterize table names, column names, or ORDER BY clauses. Dynamic SQL built from these elements still requires allowlist validation. ORMs reduce risk but can be bypassed through raw query methods.
Weekly AppSec Digest
Get new resources delivered every Monday.