WordPress: template handling
A flaw in page-template path resolution. Risk also depends on the active theme and server configuration.
Read the findings →A confirmed compromise, a vulnerable version and a documented attack are different findings. This review covers threats relevant to the sites we study, with sources showing what has been exploited.
The published analyses currently cover WordPress. Documented PrestaShop vulnerabilities are available in the PrestaShop vulnerability database. The absence of an outbreak analysis for a platform does not mean there are no threats.
A flaw in page-template path resolution. Risk also depends on the active theme and server configuration.
Read the findings →SQL injection and a REST API routing issue. Affected versions and preconditions differ between the flaws.
Read the findings →The vendor fixed an SSO login flaw. A plugin by the same vendor does not establish that Dashboard is installed.
Read the findings →WordPress describes an unauthenticated attack through page-template path resolution. CISA lists the vulnerability in its catalog of exploited flaws.
An important precondition is a top-level directory whose name starts with page- in the active parent or child theme. Full code execution requires further server-side conditions.
Install a current, supported WordPress release. Patched versions include 7.1.2, 7.0.6, 6.9.9 and 6.8.10. The vendor also backported fixes to older branches, so a lower major version alone does not establish vulnerability.
An old version without checking the theme preconditions is not enough to establish exploitability. A version match alone does not establish the cause of a compromise.
Sources: WordPress advisory and full patch list · CISA KEV
The vendor describes SQL injection in a WordPress query parameter and an issue handling batch REST API requests. Both flaws appear in CISA KEV.
The chain leading to code execution affects vulnerable releases in the 6.9 and 7.0 branches. On the 6.8 branch, SQL injection requires a theme or plugin to pass an untrusted value. The entire chain should not be attributed to every old WordPress version.
Update to a current, supported WordPress release. Fixes shipped in 7.0.2 and 6.9.5; release 6.8.6 fixes SQL injection on that branch.
An update closes a known hole. If a site was already compromised, investigation and removal of the attacker's changes are also necessary.
Sources: SQL injection advisory · REST API advisory · CISA KEV: SQLi · CISA KEV: REST API
The vendor released Dashboard 5.0.2 with an SSO login security fix. The CVE record describes an authentication bypass when Hub SSO is enabled and mapped to an administrator account.
In our September study, we saw WPMU DEV products such as Smush, Forminator or Hustle on some compromised sites. This is co-occurrence, not evidence that Dashboard was exploited.
The presence of a WPMU DEV product, including a Pro edition, does not establish the Dashboard version or login configuration. A public scan does not show that this flaw was the entry point.
We assign no victim count, first-attack date or active-campaign status to this entry. The previous description implied more than the evidence could establish.
Sources: vendor changelog · NVD CVE record · our September study, verification criteria.
An outbreak report requires evidence linking cases: a shared attack method, infrastructure or distinctive injection pattern. A CVE or a popular plugin on compromised sites is insufficient.
Each account should identify its source, observation period, attack preconditions and open questions. A KEV listing date is not the date of the first attack.
The full product and vulnerability database is in the Vulnerability radar. This review explains documented threats, so it does not grow automatically with every CVE record.
The names of compromised sites and evidence about individual domains stay private.
Open the Vulnerability radar →Sources last checked: 27 Oct 2026. Entries are editorial; statuses do not represent real-time measurement of attacker activity.
Check your site