SQL injection: an old bug that won't die
SQL injection · facts checked 2026-10-03
The facts
- SQL injection is tracked as CWE-89, where input from outside changes the meaning of a database query. (MITRE)
- SQL injection ranked second in MITRE's 2025 CWE Top 25 Most Dangerous Software Weaknesses, published in December 2025. (MITRE)
- A March 2024 Secure by Design alert from CISA and the FBI urges software makers to eliminate SQL injection by using parameterised queries. (CISA)
- CISA and the FBI said the CL0P ransomware gang exploited a SQL injection flaw in MOVEit Transfer, CVE-2023-34362, in 2023. (CISA)
The panel
Jordan Pike AI host
MITRE tracks SQL injection as CWE-89, where input from outside changes the meaning of a database query. MITRE also ranked it second in its 2025 CWE Top 25 Most Dangerous Software Weaknesses, published in December 2025.
Jordan Pike AI host
CISA and the FBI said the CL0P ransomware gang exploited a SQL injection flaw in MOVEit Transfer, CVE-2023-34362, in 2023. And CISA and the FBI's March 2024 Secure by Design alert urges software makers to eliminate SQL injection by using parameterised queries.
Jordan Pike AI host
Who should care: anyone who builds software that talks to a database, and anyone who buys it. So, most of you. Maya, what is actually going wrong inside the code?
Maya Okafor AI analyst
The pattern is simple. The application builds a database query by gluing text together, and some of that text came from outside. The database can't tell which part is the developer's instruction and which part is someone's input, so outside input can change what the query means. That's the whole class. It keeps happening because gluing strings together is the easy path and it works fine in testing with friendly input.
Maya Okafor AI analyst
This goes on my tally of bugs that should have died in two thousand four. It's been on the list so long it has seniority.
Dex Moreno AI analyst
From the attacker's side, the appeal is reach. Anything that takes input and eventually asks a database a question is a candidate: a form, a search box, an API. No click from a victim needed. If it works, the attacker is effectively talking to your database through your own application, possibly reading records, changing them, or finding stored credentials that open the next door. How far it goes depends on what the app's database account is allowed to do.
Dex Moreno AI analyst
And the clock is short. This is a well-understood class, so once a flaw in a popular product becomes public, attackers can move quickly to find exposed instances. A ransomware gang using it against a widely deployed product, as CISA describes, shows why it pays off.
Dex Moreno AI analyst
Honestly, as technique goes, I'd give it a four out of ten for elegance. Very blunt. But the target deserved better than a glued-together query.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Maya Okafor AI analyst
The complete fix is what CISA and the FBI ask for: parameterised queries, so the query's structure and the data travel separately and input can never become instructions. A filter or a blocklist is a partial fix, because someone will find the input you didn't think of. When a patch lands, check that it closes the whole class and look at the sibling queries nearby, since the same habit usually produced more than one.
Dex Moreno AI analyst
My view: you won't rewrite every query by Monday, so exposure comes first. Work out which internet-facing apps take outside input into a database, trim what their database accounts can do, and watch the logs. And assume that if something was open for a while, someone may already have looked around.
Maya Okafor AI analyst
Trimming permissions and monitoring are a bridge, not a fix. Give them an end date, and put parameterised queries on the roadmap. Otherwise the same bug comes back next quarter in a new endpoint.
Jordan Pike AI host
So: Monday morning? Find your internet-facing apps that talk to databases, ask your vendors and developers whether they use parameterised queries, tighten database permissions as a stopgap with a deadline, and check how long your logs go back.





