Although the development has taken a great deal of up-gradation in the last few years with DevOps, frameworks, automation etc. etc. etc. but still there are a number of people who still prefer the old way. Moreover, if you are starting new of just creating a college project or something like that it’s still cool to use the core PHP.The inputs in Core PHP are venerable to what you call “SQL Injection”, to before putting them to use it’s a mandatory practice to sanitize them. Below is the function you can use for the same. It’s simple, straight forward and easy to use.<h2>Benefits:</h2><ul><li>It reduces the threat of SQL injection by removing the SQL (if there is any)</li><li>It also removes the HTML tags from the data passed as some bad guys pass &lt;scripts&gt; too for some undesirable works.</li></ul><h2>Uses:</h2>Using the function is simple all you have to do is make sure that it needs&nbsp;mysql_connection&nbsp;links to function. Please make sure you provide it. Remaining is nothing to worry about.<h2>Function:</h2><pre class="ql-syntax" spellcheck="false">/**
 * protecting the input form the SQL injection and script injection.
 * @param $data
 * @return mixed
 */
public function sanitizer ($data)
{
 if (!empty($data)) {
 foreach ($data as $key =&gt; $dataValue) {
 if (empty($dataValue)) {
 continue;
 }
 $dataValue = strip_tags($dataValue);
 $data[$key] = mysql_real_escape_string($dataValue, $this-&gt;link);
 }
 }

 return $data;
}
</pre><h2>Function Call:</h2><pre class="ql-syntax" spellcheck="false">$object = new Class();
$sanitizedGetArray = $object-&gt;sanitizer($_GET);
$sanitizedPostArray = $object-&gt;sanitizer($_POST);
</pre>If you have some other things to add to this function feel free to comment, I am still learning too you know.

The inputs in Core PHP are venerable to what you call “SQL Injection”, to before putting them to use it’s a mandatory practice to sanitize them