I assume that you are using some form of database. In the DBI docs somewhere, it states that you should use placeholders for your data. For example:

# $dbh contains your database handle
my $sth = $dbh->prepare( "SELECT * FROM foo WHERE id = ? AND bar = ?" 
+) or die( "Could not prepare statement: ".$dbh->errstr() ); #of cours
+e you will have a more elegant error handling method than just die
$sth->execute( $value_for_id, $value_for_bar );
#and then just fetch the data like you would normally.
[download]

Placeholders also have the added advantage of reusing your queries. For example:

#Take the same $sth from the previous example
my @data_to_query = ( #You would probably get this from somewhere else
    { id => 763, bar => "baz" },
    { id => 923, bar => "qux" },
    #...and so forth
);

foreach( @data_to_query ) {
    $sth->execute( $_->{id}, $_->{bar} );
    #do something with that dataset
}
[download]

The advantage of that is not only performance(only need to compile SQL statement once), but the placeholders are replaced with safe data that can be used in the database. Of course, I left out several things like error handling for incorrect or malformed queries, but it is implied that you should have that.

In terms of other security, make sure you use common sense. Hash your passwords and add a salt, ensure that nobody should see data they're not supposed to see, and all other typical web security tips.
Use common sense(and common::sense) and all will be well.

"Is there any books...?"

Grammar aside, yes. Some are even referenced here: https://www.google.com/search?q=website+commerce+security&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official Doubtless Amazon, B&N or your local bookstore could suggest more. Then you could browse some, pick a few that you seem to suit your needs, and ask a far more useful and reasonable question, such as

"Are there are of these the Monks especially recommend (OR recommend against?

Is there any reason you didn't take self-help(-first) route?

As to securing scripts... depends on a host of other details you didn't tell us: who's running the server, how well hardened is it, and at what level of security is your security "good enough" for your risk level and tolerance?

PS: Fraud protection is also an important element for an e-Commerce site. Who's handling the money? Checking creditcard validity?

Such as?

I created a E-commerce site ...

Great, what is it, I'd like to steal all your money?