> jotavsec_
PT EN

← back

Outdated plugins: why WordPress sites get hacked

2026-06-10 · 3 min read
  • wordpress
  • security
  • plugins
  • best-practices

This is why people say WordPress sites are easier to hack. In this post I tell what happened on a job and what the review showed.

Context

I was hired to do some work on a client’s WordPress site. Everything went smoothly until I opened the admin panel and noticed a huge number of outdated plugins and components.

As good practice, I made a full backup of the environment before changing anything. I am glad I did: when I tried to update some components to work on a cleaner and safer base, the site simply broke.

That should not happen, but it is more common than it seems when a site goes a long time without maintenance. Restoring the backup was enough to carry on with the project.

The basic security review

After finishing the job, I did a basic security review as a bonus for the client. The result surprised me.

Scope:

  • component enumeration;
  • version identification;
  • correlation with public vulnerabilities (CVEs);
  • attack surface analysis.

There was no destructive testing and no active exploitation of any vulnerability.

Technologies identified: WordPress 6.9.4, PHP 8.1.34 and LiteSpeed Server.

WordPress itself was up to date. The problem was the plugins, which greatly widened the attack surface:

  • Elementor Pro
  • Element Pack Pro
  • ElementsKit
  • JetEngine

Besides many extremely outdated components, there were premium plugins with strong signs of missing proper licensing.

What I found

These were not theoretical vulnerabilities. The installed versions had public records of flaws of these types:

  • Remote Code Execution (RCE), critical: arbitrary code execution on the server. It can lead to full compromise of the application, malware installation and remote control of the environment.
  • SQL Injection, critical: manipulation of database queries, with risk of data leaks and tampering.
  • Privilege escalation, high: a user gets more permissions than intended, up to control of the admin panel.
  • Cross-Site Scripting (XSS), high: malicious JavaScript in the victim’s browser, with risk of session theft and admin account takeover.
  • Arbitrary file read, high: access to internal files, exposing credentials and sensitive configuration.
  • Internal information exposure, medium: makes later attacks and environment enumeration easier.

A plausible attack scenario

  1. Identify a vulnerable plugin.
  2. Exploit a known vulnerability.
  3. Gain initial access.
  4. Escalate privileges.
  5. Compromise the application.

This chain is common in poorly maintained WordPress environments. Most of the time there is no advanced technique: an update simply was not applied.

Tips

If you own a business, keep track of what gets installed on your site and be suspicious of anyone who promises dozens of premium plugins for free. If you are a developer, remember that the security of what you deliver is also your responsibility.

  • Keep WordPress, plugins and themes up to date.
  • Make periodic backups and test the restore.
  • Use a protection solution, such as Wordfence.
  • Remove plugins you do not use.
  • Use only plugins and themes from official sources.
  • Monitor and run security audits regularly.

Conclusion

Information security is no joke. Besides the technical risks, an incident can cause financial loss, reputation damage and LGPD problems. Many breaches happen not because of advanced techniques, but because an update was not applied.

Security is a continuous process, not a one-off action.

achievements

This site hides 15 achievements. Press ` to open the terminal. The ★ button shows your progress and hints.

How do you want to view the site?

You can switch anytime in the header.