WordPress plugin
Custom Comment 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
- Medium2
- Low0
All Custom Comment vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤2.1.6No patch available | CVE-2025-48365 | |
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤2.1.6No patch available | CVE-2025-49889 |
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤2.1.6No patch available
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤2.1.6No patch available
Custom Comment: common questions
Does Custom Comment have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in Custom Comment: 2 medium. At least one is not fixed in the latest version.
How do I check which version of Custom Comment 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 Custom Comment vulnerability?
CVE-2025-48365, published Aug 20, 2025: Custom Comment <= 2.1.6 - Authenticated (Administrator+) Stored Cross-Site Scripting. Severity: Medium (CVSS 4.4).
Is any Custom Comment vulnerability listed in CISA KEV?
No. None of the known Custom Comment vulnerabilities is currently listed in the CISA KEV catalog.