Security snapshot
Across 5 js_composer111 WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 5 indexed WordPress sites with js_composer111, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 60% versus 38.5% overall (+21.5 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 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_composer111, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
js_composer111 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 |
|---|---|---|---|
| a*k*s*a*t*m*t*o*s.com (WP 6.4.10) | F | Sep 8, 2026 | |
| s*n*u*l*s*e*t*p*l*.com (WP 7.1) | F | Aug 30, 2026 | |
| a*f*e*e*t*i*c*r*o*a*i*n.com (WP 7.0.4) | F | Aug 27, 2026 | |
| a*s*n*e*h.ir (WP 6.5.8) | F | Aug 2, 2026 | |
| f*r*i*g*r*s*e*.com (WP 7.0.2) | F | Jul 30, 2026 |