WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: ajaxified-cart-woocommerce (Used by 58 domains)

Security snapshot

Across 58 ajaxified-cart-woocommerce WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 3% Grade C 0% Grade D 2% Grade F 93%
Fail the header check (F)93%vs 82.5% avg
Leak usernames36%vs 38.5% avg
Expose a sensitive file3.4%vs 1.8% avg
Use HTTPS95%vs 96.2% avg

What stands out

TLDWP currently associates 58 indexed WordPress sites with ajaxified-cart-woocommerce, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 93.1% versus 82.5% overall (+10.6 percentage points).

Username enumeration is 36.2% vs 38.5% overall (-2.3 pp); Sensitive-file exposure is 3.4% vs 1.8% overall (+1.6 pp); HTTPS adoption is 94.8% vs 96.2% overall (-1.4 pp).

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

Ajaxified Cart

πŸ‘€ Abhishek Kumar πŸ”— Plugin Homepage

WooCommerce core does not provide AJAX add-to-cart on the single product page or for variable products listed on archive pages (it redirects to the single view). This plugin adds an unobtrusive AJAX workflow for: Simple products (single product page button becomes AJAX) Variable products on archive & block-based Product Collection (opens an accessible modal to choose attributes, then adds via AJAX) Classic themes and modern block/FSE themes (2025 and later) with Product Collection blocks Highlights: * Works with…

Domain Exposures Headers Last Checked
k*l*y*s*.com F Sep 9, 2026
l*c*y*y*t*m*.ru F Sep 9, 2026
s*w*e*t*m*a.com (WP 7.1) F Sep 9, 2026
d*v*n*i*m*n.com (WP 4.9.31) F Sep 8, 2026
m*t*.me (WP 6.8.3) B Sep 8, 2026
e*k*.site F Sep 7, 2026
f*u*m*n*.ru (WP 6.6.7) F Sep 5, 2026
e*r*w*t*h*a*i*g*t*r*.com (WP 7.1) F Sep 5, 2026
d*c*r*-*n*i*e*r*n*.ru (WP 6.7.7) F Sep 5, 2026
e*h*o*-*e*u*y.com (WP 7.0.4) F Sep 4, 2026
t*s*a*x*e*r.com (WP 7.0.4) F Sep 2, 2026
x*-*9*b*6*d*.com F Sep 2, 2026
r*s*u*i*s*o*.com (WP 4.9.31) F Sep 1, 2026
a*s*k*z*e*s*v*.com (WP 7.1) F Sep 1, 2026
s*o*w*l*p*p*r*i*l.com (WP 7.1) F Aug 29, 2026
c*e*t*u*.com (WP 6.4.10) F Aug 28, 2026
2*h*u*s*p*.hk (WP 4.9.31) F Aug 26, 2026
o*d*r*e*i*.cz (WP 5.6) F Aug 25, 2026
b*r*a*i*g*r*e.com (WP 7.0.4) F Aug 25, 2026
s*a*e*n*a*e*e*s.com (WP 4.9.26) F Aug 24, 2026
k*2*f*o*.ru F Aug 24, 2026
h*p*u*.shop (WP 7.1) F Aug 22, 2026
s*v*n*r*.com (WP 5.4.2) F Aug 22, 2026
m*b*g*o*l.com F Aug 21, 2026
i*d*s*r*-*a*t*-*n*.com F Aug 20, 2026
t*o*.ru (WP 7.0.4) F Aug 19, 2026
g*l*n*p*d*o*k*.com (WP 7.0) F Aug 19, 2026
v*p*n*a*o*.com D Aug 18, 2026
p*r*e*-*t*l*.com (WP 6.6.7) F Aug 18, 2026
e*o*e*.ru (WP 7.0.2) A Aug 17, 2026
s*p*i*i*o*k*a.com F Aug 16, 2026
s*p*i*-*r*s*o*a*.com F Aug 16, 2026
p*t*d*p*m*e.com (WP 7.0.4) F Aug 15, 2026
t*e*m*l*x.de F Aug 4, 2026
v*z*o*i*.ru (WP 5.8.13) F Aug 4, 2026
a*k*r*5*.ru (WP 7.0.2) F Aug 4, 2026
c*n*o*m*i*.no F Aug 3, 2026
c*y*t*n*s*.ru F Aug 3, 2026
a*b*k*-*i*i*a.ru (WP 7.0.2) F Aug 3, 2026
n*k*e*m*.ru (WP 7.0) F Aug 1, 2026
v*t*b*e*k*h.ru F Jul 30, 2026
d*e*a*h*u*h*s*k*.ru F Jul 29, 2026
k*s*c*n*e*.ru F Jul 28, 2026
v*p*a*e*i*g*f*o*b*x.com F Jul 26, 2026
v*p*a*e*i*g*a*e*d*.com F Jul 26, 2026
f*t*d*c*r.com (WP 7.0.2) F Jul 26, 2026
s*r*m*o*e.com F Jul 26, 2026
c*u*h*m*.com (WP 6.9.5) F Jul 25, 2026
s*e*o*d*s*.com (WP 7.0.2) F Jul 23, 2026
k*k*k*s*e*i*a.ru (WP 6.2.2) F Jul 23, 2026
a*u*a.o*g.uk (WP 7.0.2) F Jul 23, 2026
p*o*a*r*m*n*o.org (WP 7.0.2) F Jul 21, 2026
m*r*i*s*a*.com (WP 6.7.2) B Jul 20, 2026
s*n*c*y*t.ru F Jul 20, 2026
e*e*.store (WP 6.1.10) F Jul 19, 2026
b*o*s*u*d.com (WP 7.0.2) F Jul 19, 2026
d*c*r*-*n*i*e*r*n*.com (WP 6.7.5) F Jul 19, 2026
z*d*s*o*t.ru (WP 7.0.2) F Jul 18, 2026