WebGee DocsDocs
Security & SSL
Free migration + 30-day money-backSee how

Resolve a cPGuard CMS threats report

Read the "Threats to CMS installations detected" email, find the plugin or theme behind it in cPanel, and update or remove it.

cPGuard checks every WordPress, Joomla and Drupal installation in your account for known vulnerabilities and emails you a summary each week. Applies to shared, reseller and Premium hosting on cPanel.

The email is titled Threats to CMS installations detected. It tells you that an installation has a problem, not which plugin or theme causes it. The detail is in cPanel, and this article takes you to it.

Read the email

The four numbers at the top count problems across the whole account:

CounterWhat it means
Critical CMS IssuesInstallations with at least one known vulnerability
Updates PendingInstallations whose core version is out of date
CMS threatsMalicious files found inside an installation
Database infectionsMalicious content found in an installation's database

The table below them lists each affected installation. Two columns are easy to misread together:

  • Status describes the CMS core only. latest means WordPress, Joomla or Drupal itself is up to date.
  • CVE is the most severe known vulnerability anywhere in the installation, which usually means a plugin or theme. The score is out of 10: 4.0 to 6.9 is Medium, 7.0 to 8.9 is High and 9.0 or more is Critical.

So a row showing latest next to High, Score: 7.5 is not a contradiction. The core is current, but something installed on top of it has a published vulnerability.

If CMS threats or Database infections is above zero, the site is already infected, not just exposed. Go straight to Clean malware from your website.

Find what is vulnerable

  1. In cPanel, type cPGuard into the Search Tools box and open it.

  2. Select CMS Threats.

    The CMS Reports page, with one installation showing a CVE of 7.5 High and 1 of 14 plugins outdated

  3. Find the installation from the email. CVE shows its worst score, Plugins shows how many are outdated, and Issues counts everything cPGuard found.

  4. Select the installation to open CMS Details.

    CMS Details for an installation, with the Plugins tab open and one plugin's version shown in red with an update available

  5. Work through the tabs. A number on a tab means it has something to look at:

    • Plugins and Themes — a version in red with yes under Update available is outdated. A score in the CVE column, instead of Safe, is the vulnerability the email reported.
    • Core issues — problems with the CMS itself.
    • Threats — malicious files. Anything here means cleaning the site, not just updating it.

Note the name of each plugin or theme with a CVE score. You need them in the next section.

Fix it

Take a backup of the site first. An update that breaks the site is easier to undo than to fix.

  1. Log in to the site's admin area. For WordPress, that is /wp-admin.
  2. For WordPress, open Dashboard > Updates. For Joomla or Drupal, open the extensions or updates page.
  3. Update each item you noted at the end of the previous section.
  4. If an item has a CVE score but no update is available, the author has not fixed it yet. Deactivate and delete it, and replace it with an alternative that is maintained.
  5. Delete any plugin or theme you no longer use, including inactive ones.

Deactivating a plugin does not protect you. Its files stay on the server and can still be reached directly, which is how most of these vulnerabilities are exploited. If you do not use it, delete it.

Confirm it worked

  1. In the site's admin area, the updates page shows nothing pending.
  2. In CMS Threats, open the installation again. The items you updated show Safe in the CVE column.

cPGuard re-checks installations on its own schedule, so the page can take a little while to catch up. Your next weekly email should no longer list the installation.

If it is still listed

  • You do not recognise the installation. Old copies of a site, such as public_html/old or a forgotten staging folder, are scanned too and are a common way in. If you no longer need the copy, delete its folder and its database.
  • The update fails. The plugin may require a newer PHP version than the site runs, or the update may be blocked by file permissions. Check the plugin's requirements, then see File and directory permissions.
  • Every item shows Safe but the email keeps arriving. Open a ticket with your support PIN and the installation path, and we will look at the report with you.

On this page

Hosted elsewhere?

Cloud Hosting

cPanel on NVMe storage, with LiteSpeed, free SSL and daily backups included.

See plansFree migration