Outdated Content Management System or Plugins

The content management system, or plugins, themes or modules installed in it, is an outdated release with publicly known vulnerabilities, some exploitable without logging in.

SeverityHigh
CVSS 3.18.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1190 Exploit Public-Facing Application
CategoryOutdated Components

Description

The site runs an outdated release of a content management system (CMS), such as WordPress, Drupal or Joomla, or outdated plugins, themes, extensions or modules installed in it, for which security fixes have been published. CMS add-ons are written by many independent developers and are a frequent source of serious flaws, such as SQL injection, arbitrary file upload, privilege escalation and authentication bypass, and some have been abandoned by their authors and will never receive a fix.

Flaws that need no authentication, such as SQL injection, arbitrary file upload or remote code execution in the core or a plugin, can give an attacker control of the site and the server it runs on, access to its database, including user accounts and personal data, and a platform for defacement, malware distribution or attacks on visitors. Exploit code for popular add-ons is often published soon after a fix, and automated campaigns, which scan the internet for vulnerable CMS installations, often exploit them soon after it becomes public, so exposure does not depend on the site being chosen as a target.

Versions can be identified from generator meta tags, readme and changelog files, version parameters added to script and stylesheet addresses, and characteristic files, using tools such as WPScan, droopescan or JoomScan, and then matched against vendors' advisories and vulnerability databases. The impact depends on the flaws present, so each identified flaw should be checked for its preconditions, since many need a particular configuration or an authenticated account with a given role; flaws that need an account are a lesser but real risk, particularly where the site allows public registration.

Remediation

Bring the CMS and every add-on up to date, and keep them there:

  • Update the CMS core to the latest supported release, then each plugin, theme, extension and module, testing on a staging copy first where the site is complex. Move off any major version that is no longer supported.
  • Remove add-ons that are not in use, including deactivated ones, whose files remain on the server and may still be reachable, and replace any that are abandoned or have unfixed flaws.
  • Turn on automatic updates for security releases where the platform supports them, and follow the security advisories for the CMS and its add-ons.
  • Keep an inventory of the add-ons and versions in each installation and include them in regular vulnerability scanning.
  • Limit the damage of a future flaw: restrict access to the administration interface, require strong passwords and multi-factor authentication for privileged accounts, disable file editing from the administration interface, and set file permissions so that the web server cannot write to the site's code.

Where an update must wait, a web application firewall with rules for the specific flaws can reduce the risk in the meantime, but it is not a substitute for updating. Confirm the fix by rescanning the site and checking the reported versions of the core and each add-on against the current releases.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding