Security snapshot
Across 6 js_composers WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 6 indexed WordPress sites with js_composers, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.5% overall (-38.5 percentage points).
HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Header-grade F is 83.3% vs 82.5% overall (+0.8 pp).
These are observational associations among sites where TLDWP detected js_composers, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
js_composers Premium / Custom
This plugin is not available on WordPress.org. It may be a premium plugin, a custom plugin, or a plugin from a third-party marketplace.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| m*t*h*w*m*g*c.c*.uk (WP 7.1) | F | Sep 6, 2026 | |
| v*e*m*c*i*e.c*m.vn (WP 7.1) | D | Sep 4, 2026 | |
| l*n*l*m*s*i*.no (WP 6.4.3) | F | Sep 3, 2026 | |
| b*t*e*f*x*e.com (WP 6.6.2) | F | Aug 28, 2026 | |
| c*f*-*f*b.com (WP 5.8.13) | F | Aug 2, 2026 | |
| i*s*i*u*o*u*o*e*d*l*o*e*i*a*.com | F | Jul 25, 2026 |