Talk:SQL injection
How you can help:
| This is the talk page for discussing improvements to the SQL injection article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Archives: 1 |
 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||
| ||||||||||||||||||||||||||
 | On 26 May 2026, it was proposed that this article be moved from SQL injection to SQL injection attack. The result of the discussion was not moved. |
There seems to be an example missing in the Mitigations > Escaping subsection
Nothing comes after the sentence 'the following example parameterizes a SQL query by escaping username and password parameters:' Vladmashk (talk) 13:12, 30 August 2024 (UTC)
- This edit removed it. I've undone that edit, so it's back now. -- WOSlinker (talk) 14:39, 30 August 2024 (UTC)
Substantial changes
I took the liberty to make some changes, which, I believe, make the article more consistent. Being inexperienced Wikipedia contributor, I am not sure if my contributions violate some regulations. If so, please do not revert them in bulk, or at least don't do that without a discussion, in which I would get a chance to defend the changes I made or learn how to improve them up to Wikipedia standards. Thank you. 95.24.174.50 (talk) 12:01, 13 December 2024 (UTC)
Move to SQL injection attack?
Requested move 26 May 2026
- The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.
The result of the move request was: not moved. (closed by non-admin page mover) Jeffrey34555 (talk) 06:56, 2 June 2026 (UTC)
SQL injection → SQL injection attack – A lot of the other types of computer hacking techniques are referred to as "attacks" or "hacks" such as Denial-of-service attack, WannaCry ransomware attack, or Viasat hack. Also, SQL injection is only used in the context of an attack. VidanaliK (talk to me) (contributions) 16:14, 26 May 2026 (UTC)
- Oppose Per WP:CONCISE and WP:COMMONNAME. There is no need to add the additional explanatory "attack" to the name, that is explained within the article quickly. ᴢxᴄᴠʙɴᴍ (ᴛ) 05:13, 27 May 2026 (UTC)
- Oppose: per nom as it is already mentioned in the article. ~ŤheŴubṂachine-840≈ ● ✒️ 09:35, 27 May 2026 (UTC)
- Comment I would point out that ransomware and Social_engineering_(security), Trojan_horse_(computing) and phishing avoid the suggested pattern. Joe (talk) 16:54, 27 May 2026 (UTC)
- Oppose The article is only about SQL injection. If "attack" is added, the reader would expect a real world incident or example of a SQL injection attack. Also per WP:CONCISE.
Welovecontributors! [talk] 02:00, 2 June 2026 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.