WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: comment-report-button-modified-with-spampos (Used by 2 domains)

Security snapshot

Across 2 comment-report-button-modified-with-spampos WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 0% Grade F 100%
Fail the header check (F)100%vs 82.5% avg
Leak usernames100%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

TLDWP currently associates 2 indexed WordPress sites with comment-report-button-modified-with-spampos, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 100% versus 38.5% overall (+61.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 comment-report-button-modified-with-spampos, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

Similar security profiles

Closest among widely detected plugins by average difference across header-grade F, username enumeration, exposed-file, and HTTPS rates.

bluehost-wordpress-plugin 188,361 sites 13.3 pp avg difference gutenberg 146,899 sites 14.8 pp avg difference jetpack 416,614 sites 15.8 pp avg difference astra-sites 107,145 sites 17.3 pp avg difference

Profile similarity reflects these four observed rates only; it does not imply a technical relationship, shared ownership, or causation.

Explore more TLDWP data: Plugins Themes PHP versions Servers CDNs / WAFs
Domain Exposures Headers Last Checked
z*z*o*u.com F Sep 4, 2026
t*s*s*k*.com F Jul 20, 2026
Copyright 2026, tldwp.com. All rights reserved. Data Use License · WordPress maintenance or security needs? Reach out!