WordPress plugin
Stopwords for comments security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Stopwords for comments vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Missing Authorization to Cross-Site Request Forgery ≤1.1No patch available | CVE-2025-15376 |
- Medium4.3Missing Authorization to Cross-Site Request Forgery
≤1.1No patch available
Stopwords for comments: common questions
Does Stopwords for comments have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Stopwords for comments: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Stopwords for comments I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Stopwords for comments vulnerability?
CVE-2025-15376, published Jan 13, 2026: Stopwords for comments <= 1.1 - Missing Authorization to Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any Stopwords for comments vulnerability listed in CISA KEV?
No. None of the known Stopwords for comments vulnerabilities is currently listed in the CISA KEV catalog.