Security snapshot
Across 8 js_composernew WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 8 indexed WordPress sites with js_composernew, 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 100% vs 82.5% overall (+17.5 pp); Sensitive-file exposure is 12.5% vs 1.8% overall (+10.7 pp); HTTPS adoption is 87.5% vs 96.2% overall (-8.7 pp).
These are observational associations among sites where TLDWP detected js_composernew, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
js_composernew 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 |
|---|---|---|---|
| e*p*t*e*t.com (WP 7.0.4) | F | Sep 7, 2026 | |
| l*o*i*g*l*o*a*i*e.com | F | Aug 31, 2026 | |
| p*r*u*i.gr | F | Aug 20, 2026 | |
| a*t*o*b*l*b*v*r*y.com (WP 4.8.25) | F | Jul 30, 2026 | |
| l*t*l*e*d*p*y*a*e.fr (WP 5.2.24) | F | Jul 27, 2026 | |
| c*b*n*t*e*p*r*o.com (WP 6.8.6) | F | Jul 24, 2026 | |
| c*a*l*t*e*e*a*i*c*a*i*g*.com (WP 6.3.8) | F | Jul 20, 2026 | |
| e*p*u*b*n*c*r*.com | F | Jul 20, 2026 |