WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: custom-sidebars (Used by 59 domains)

Security snapshot

Across 59 custom-sidebars WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 2% Grade F 98%
Fail the header check (F)98%vs 82.6% avg
Leak usernames59%vs 38.6% avg
Expose a sensitive file10.2%vs 1.8% avg
Use HTTPS86%vs 96.3% avg

What stands out

TLDWP currently associates 59 indexed WordPress sites with custom-sidebars, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 59.3% versus 38.6% overall (+20.7 percentage points).

Header-grade F is 98.3% vs 82.6% overall (+15.7 pp); HTTPS adoption is 86.4% vs 96.3% overall (-9.9 pp); Sensitive-file exposure is 10.2% vs 1.8% overall (+8.4 pp).

These are observational associations among sites where TLDWP detected custom-sidebars, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

Custom Sidebars

๐Ÿ‘ค WebFactory ๐Ÿ”— Plugin Homepage

Manage and replace sidebars and other classic widget areas on your site with Custom Sidebars, a flexible widget area manager. Make custom sidebar configurations and be able to choose what classic widgets display on each page or post of your site. Need to make a widget sticky or fixed? Try our free WP Sticky Anything plugin. Custom Sidebars works ONLY with the classic widgets screen that was used in WordPress before version 5.8.โ€ฆ

Domain Version Exposures Headers Last Checked
s*o*t*e*-*s.com (WP 4.9.8) F Sep 10, 2026
k*t*l*c*r*b*g*g*l*s.com (WP 6.5.10) 3.1.2· 85% conf. F Sep 10, 2026
m*r*i*m*j*a*.com (WP 4.8.25) F Sep 8, 2026
k*d*c*u*t*y*a*l*s.com (WP 4.7.5) F Sep 6, 2026
b*o*s*l*i*g*n*v*r*i*y.com (WP 5.4.21) F Sep 6, 2026
y*g*s*y*e*a*i*.com (WP 4.7.35) F Sep 5, 2026
m*t*r*s*e*p*.com (WP 4.7.29) F Sep 5, 2026
a*a*t*r*i*i*.com (WP 4.7.15) F Sep 5, 2026
m*s*e*.c*m.my F Sep 5, 2026
m*s*i*u*n*n*.com (WP 4.6.29) F Sep 3, 2026
t*m*i*s*n*a*l*c.com (WP 4.7.29) F Aug 29, 2026
r*c*e*n.com (WP 5.5.20) F Aug 29, 2026
t*n*t*c.com (WP 4.8.25) F Aug 28, 2026
c*a*g*a*b*r*t*e*a*y.com F Aug 28, 2026
l*t*h*i*l*b*u*s.com (WP 4.7.29) F Aug 27, 2026
e*e*g*n*i*i*a.com (WP 4.5.16) F Aug 27, 2026
l*s*-*e*i*.com (WP 4.7.35) F Aug 27, 2026
s*e*e.com (WP 5.2.5) F Aug 26, 2026
e*i*a*e*h*w*l*o*.com (WP 4.7.35) F Aug 25, 2026
w*s*w*y*o*n*.com F Aug 24, 2026
a*v*n*p*o*e*t*e*l*c.com (WP 7.1) F Aug 22, 2026
g*s*r*n*x*.com (WP 4.9.31) D Aug 21, 2026
c*m*r*s*i*n*r*d*c*s.com F Aug 20, 2026
p*t*v*d*t*l.eu (WP 4.7.35) F Aug 20, 2026
i*d*s*h*l*.com F Aug 20, 2026
b*y*i*e*s*r*u*.com (WP 4.8.1) F Aug 19, 2026
m*g*a*r*n.ru (WP 4.7.2) F Aug 19, 2026
a*f*r*a*i*9*.com (WP 4.7.35) F Aug 18, 2026
i*s*i*u*s*h*a*z*o*f.de (WP 6.8.8) F Aug 17, 2026
j*y*1.com (WP 4.7.29) F Aug 16, 2026
v*e*e*i*g*o*p.com F Aug 14, 2026
s*l*i*m*a*c*n*t*u*t*o*s.com (WP 4.6.29) F Aug 14, 2026
u*3*-*h*s*o.com (WP 6.2.2) F Aug 14, 2026
s*r*t*3*u*i*e*s*t*.com F Aug 9, 2026
m*x*o*s*.com F Aug 9, 2026
h*b*t*t*u*t*n*a*l*.com (WP 4.7.26) F Aug 7, 2026
k*n*e*a*i*b*d*o*z*z.eu F Aug 6, 2026
l*u*n*e*g*r*m*l*r*i.ch F Aug 5, 2026
p*v*m*n*t*p*r*s.org (WP 4.9.1) F Aug 4, 2026
z*-*m*o*t.com (WP 7.0) F Aug 3, 2026
s*o*o*.ru F Aug 2, 2026
g*a*s*s*a*d.c*.kr F Jul 30, 2026
c*r*i*g*h*u*e*t*d*o*.com F Jul 30, 2026
c*r*i*g*h*u*e*u*i*.com F Jul 30, 2026
p*i*r*t*m*n*s*r*e*.com (WP 4.9.29) F Jul 29, 2026
v*-*r*n*p*r*.com (WP 4.7.6) F Jul 29, 2026
h*p*g*.com F Jul 29, 2026
e*g*m*d.net F Jul 29, 2026
c*r*e*f*t*a*e*.c*.uk F Jul 28, 2026
t*x*-*l*i.com (WP 4.7.33) F Jul 27, 2026
n*u*i*m*l*r*i.ch F Jul 27, 2026
g*e*t*a*l*o*g*n*z*r*.com (WP 7.0.2) F Jul 26, 2026
i*s*i*u*s*h*a*z*o*f.com (WP 6.8.6) F Jul 25, 2026
s*r*t*.com F Jul 25, 2026
d*s*r*b*i*o*a*a*y*r*.com (WP 5.3.21) F Jul 24, 2026
i*n*v*m*c*.com (WP 4.6.30) F Jul 24, 2026
b*s*a*a*d*r*.com (WP 4.7.5) F Jul 22, 2026
h*n*m*d*l*v*s.com F Jul 22, 2026
h*m*t*c*-*r*.com (WP 4.7.33) F Jul 21, 2026