Content Censor
Content Censor has one disclosed vulnerability in the WordSec catalog, all reported in 2023; it is fixed as of September 2026. Their average CVSS score is 4.4, and the most serious one scores 4.4 out of 10.
The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).
The one issue recorded for Content Censor has a vendor fix available, so running the current release closes it.
All of these findings were reported by yuyudhn. Content Censor is installed on roughly 500 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.0.4.
CVE-2023-23883WP Content Filter – Censor All Offensive Content From Your Site <= 3.0.1 - Authenticated (Administrator+) Stored Cross-Site Scripting
Read the full analysisVulnerability Records

Content Censor
Author
gwycon
Content Censor replaces configured words when WordPress displays supported content. Your original posts, pages, and comments remain unchanged in the database, so authorised editors can continue to work with the source text. Use the settings page to: define the words to filter; choose whole-word or embedded matching; select case-sensitive or case-insensitive matching; choose a replacement character and masking style; enable filtering for content, excerpts, titles, comments, author names, tags, and tag clouds; and exclude selected post or page IDs. Content Censor is a presentation-layer filter. It does not replace appropriate permissions, moderation, reporting, or security controls. Upgrade to Content Censor Pro for batched site scanning, browser-title and BuddyPress filtering, custom hook support, automatic updates, and priority support: https://wpgoplugins.com/plugins/content-censor/
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C