WP Stop Profanity Security & Risk Analysis

wordpress.org/plugins/wp-stop-profanity

Stops Profanity on your site by allowing you to select the words that you want blacked out.

10 active installs v0.5 PHP + WP 2.0.2+ Updated Nov 8, 2010
commentsfilterprofanitythe_contentthe_title
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Stop Profanity Safe to Use in 2026?

Generally Safe

Score 85/100

WP Stop Profanity has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 15yr ago
Risk Assessment

The "wp-stop-profanity" plugin v0.5 exhibits a generally good security posture based on the provided static analysis. It has a remarkably small attack surface with no identified AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, none of these entry points are unprotected. The plugin also demonstrates good practice by not using raw SQL queries and exclusively employing prepared statements. Furthermore, it does not engage in file operations or external HTTP requests, minimizing potential vectors for compromise. The absence of known CVEs and a clean vulnerability history are also strong indicators of a well-maintained and secure plugin.

Key Concerns

  • Dangerous function 'unserialize' used
  • Output not properly escaped
  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

WP Stop Profanity Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

WP Stop Profanity Release Timeline

v0.5Current
v0.4
v0.3
v0.2
Code Analysis
Analyzed Apr 16, 2026

WP Stop Profanity Code Analysis

Dangerous Functions
4
Raw SQL Queries
0
0 prepared
Unescaped Output
2
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Dangerous Functions Found

unserialize$words = unserialize(get_option('wp_profanity_words'));wp-stop-profanity.php:25
unserialize$words = unserialize(get_option('wp_profanity_words'));wp-stop-profanity.php:44
unserialize$words = unserialize(get_option('wp_profanity_words'));wp-stop-profanity.php:63
unserialize$words = unserialize(get_option('wp_profanity_words'));wp-stop-profanity.php:97

Output Escaping

0% escaped2 total outputs
Attack Surface

WP Stop Profanity Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
filterthe_contentwp-stop-profanity.php:38
filtercomment_textwp-stop-profanity.php:57
filterthe_titlewp-stop-profanity.php:76
Maintenance & Trust

WP Stop Profanity Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedNov 8, 2010
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP Stop Profanity Developer Profile

matthewprice1178

2 plugins · 40 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect WP Stop Profanity

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
profanityWordsformItemtextInput
Shortcode Output
<span style="padding: 0 3px 0 3px;background: #000000; color: #FFFFFF;">&bull;&bull;&bull;&bull;</span>
FAQ

Frequently Asked Questions about WP Stop Profanity