WordPress plugin
WebPurify Profanity Filter security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 1 known vulnerability is fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium1
- Low0
All WebPurify Profanity Filter vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.5 | Missing Authorization to Unauthenticated Plugin Settings Change via webpurify_save_options ≤4.0.2Update to 4.0.3 | CVE-2026-0572 |
- Medium6.5Missing Authorization to Unauthenticated Plugin Settings Change via webpurify_save_options
≤4.0.2Update to 4.0.3
WebPurify Profanity Filter: common questions
Does WebPurify Profanity Filter have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in WebPurify Profanity Filter: 1 medium. None are known to affect version null.
How do I check which version of WebPurify Profanity Filter 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 WebPurify Profanity Filter vulnerability?
CVE-2026-0572, published Feb 3, 2026: WebPurify Profanity Filter <= 4.0.2 - Missing Authorization to Unauthenticated Plugin Settings Change via webpurify_save_options. Severity: Medium (CVSS 6.5).
Is any WebPurify Profanity Filter vulnerability listed in CISA KEV?
No. None of the known WebPurify Profanity Filter vulnerabilities is currently listed in the CISA KEV catalog.