An SQL injection targets the WordPress database. In the process, data is added, modified or just retrieved – by hackers! What is the danger of an SQL injection? How does a hacker earn from an SQL Database injection? What is the danger in an SQL injection? And what can you do against an SQL injection? You can read about it in this article!
What is the danger of an SQL injection?
- An SQL injection allows a hacker to add data to the database
The hacker injects a new WordPress user, an administrator.
This allows him to log into your website’s backend and do anything he wants.
- Through an SQL injection a hacker can modify information in your database
The hacker can thus modify the existing administrator accounts, the password is changed and thus the hacker can simply log into the back-end of WordPress.
- A hacker can delete information from your database
This may not be the biggest problem of the 3. In fact, it is rare because there is nothing to gain for the hacker. But if you lose your posts and pages … and you don’t have a backup … you still have a huge problem!
How does a hacker earn from an SQL Database injection?
When you know why a hacker does this, you understand that the risk of an SQL injection is something you absolutely must avoid.
Here we discuss some types of websites, and the common injections:
Suppose you have a web shop
Then an SQL injection can cause your payment details to be changed TO THOSE OF THE HACKER!
> Malware enters the website that you have to remove.
> The customer has paid so you have to deliver your product or service.
> You don’t get paid a dime.
> The scumbag (the hacker) gets the money deposited into his account.
Suppose you have a small business website
Small business owners are so not easily aware of the danger, but also underestimate what it costs if visitors refer the website to another unsavory website.
> Malware gets into the website that you have to remove (or have removed)
> The hacker redirects visitors with a redirect script.
> You lose your visitors, who can no longer purchase services from you. Visitors have absolutely no idea why your website is off their screen.
> Visitors no longer return to your website.
> The hacker has a website., web shop or an SEO client where all the visitors go.
In the case of a large corporate website
It took a lot of time to set up a business with a good reputation, there are a lot of visitors. An advertising (SQL database) injection unfortunately changes.
> Malware enters the website that you have to remove (or have removed).
> Visitors get to see advertisements or are redirected.
> You have lost your new potential customer.
> The established customer experiences that you don’t have your “online business” in order.
> Your reputation (ranking) in Google goes down, resulting in fewer visitors.
The risk calculator!
I haven’t added this before in the previous 300+ articles, but to add nuance and put the risks in perspective, herewith THE RISK CALCULATOR.
- 5 plugins – Don’t worry, but keep them up to date and WordPress of course too!
10 plugins – Pay close attention to which ones you use (wpscan.com)
15 plugins – No problem yet, watch wpscan.com, update them, delete plugins that are no longer updated by plugin builders.
20 plugins – I hope you have a web shop? For an informative website, limit the number as much as possible. Keep plugins up-to-date, check monthly wpscan.com to see if they are still safe.
25 plugins – Then get someone to maintain your website. You run a lot of risk at 25 plugins and more. Reduce the number, or hire a security person who will check everything for you, update, check your website status in Google, scan your website regularly.
30 plugins and more – Can be done, but get someone to maintain your website intensively!!!
What can you do against an SQL database injection?
- BACKUP – Make sure you have daily, weekly or MINIMUM monthly backups.
- SCAN – It is always recommended to scan your website monthly with the Sucuri malware scanner & Isithacked.
- EXPERT – You’re going to forget to scan, hire someone to do that 7 days a week. (WPProtect, or another).
- INSTALL A SECURITY SPLUGIN – Not 2, no. Just 1. Think WordFence, iThemes, Sucuri. And configure those properly according to your website.