Mention that this is also true for POST (from a note by Mark Coudill).

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@333406 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Derick Rethans 2014-04-22 13:29:46 +00:00
parent 2fab4d7888
commit 0724a1791b

View file

@ -7,9 +7,10 @@
<section>
<title>Request Injection Attacks</title>
<para>
If you are passing <literal>$_GET</literal> parameters to your queries, make
sure that they are cast to strings first. Users can insert associative
arrays in GET requests, which could then become unwanted $-queries.
If you are passing <literal>$_GET</literal> (or <literal>$_POST</literal>)
parameters to your queries, make sure that they are cast to strings first.
Users can insert associative arrays in GET and POST requests, which could
then become unwanted $-queries.
</para>
<para>
@ -28,9 +29,9 @@
</para>
<para>
This is a fairly easy attack to defend against: make sure $_GET's parameters
are the type you expect before you send them to the database (cast them to
strings, in this case).
This is a fairly easy attack to defend against: make sure $_GET and $_POST
parameters are the type you expect before you send them to the database
(cast them to strings, in this case).
</para>
<para>