Security snapshot
Across 8 js_composer_2 WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 8 indexed WordPress sites with js_composer_2, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 62.5% versus 38.5% overall (+24 percentage points).
Header-grade F is 62.5% vs 82.5% overall (-20 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected js_composer_2, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
js_composer_2 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 |
|---|---|---|---|
| s*u*h*h*l*y*l*m*i*g.com (WP 6.8.8) | C | Sep 8, 2026 | |
| t*a*p*t*.com (WP 4.7.20) | C | Sep 3, 2026 | |
| j*k*e*a*.com | F | Aug 16, 2026 | |
| a*j*e*.c*m.ar (WP 5.8.14) | F | Aug 9, 2026 | |
| a*i*a*e*a*i.com (WP 5.6.17) | F | Aug 1, 2026 | |
| c*k*o*e.com (WP 4.7.20) | C | Jul 26, 2026 | |
| v*n*i*f*s*i*n.com | F | Jul 25, 2026 | |
| s*e*e*i*t*a*.com | F | Jul 22, 2026 |