ContentPen Security & Risk Analysis

wordpress.org/plugins/contentpen

AI-Powered SEO Content Writing Assistant

200 active installs v1.0.11 PHP 7.4+ WP 5.8+ Updated Feb 18, 2026
aibloggingcontent-marketingcontent-writingseo
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is ContentPen Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The "contentpen" v1.0.11 plugin exhibits a strong security posture based on the static analysis. The absence of any identified attack surface entry points, particularly those lacking authentication checks, is a significant positive. Furthermore, the code signals indicate good development practices, with a high percentage of SQL queries using prepared statements and output being properly escaped. The presence of nonce and capability checks further bolsters its defense against common WordPress vulnerabilities. The lack of any recorded vulnerabilities in its history is also a very positive indicator of the plugin's security reliability over time.

While the static analysis reveals no critical or high severity issues, the presence of raw SQL queries, even if a minority, warrants a minor deduction. The single file operation and external HTTP request, while not inherently vulnerable, represent potential areas for future exploitation if not handled with extreme care and validation. The taint analysis reporting zero flows is excellent, suggesting that data is being handled securely within the plugin.

In conclusion, "contentpen" v1.0.11 appears to be a well-developed and secure plugin. Its minimal attack surface, robust code signals, and clean vulnerability history are commendable. The few minor areas for attention do not detract significantly from its overall strong security rating.

Key Concerns

  • SQL queries without prepared statements
Vulnerabilities
None known

ContentPen Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

ContentPen Code Analysis

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

SQL Query Safety

67% prepared3 total queries

Output Escaping

97% escaped32 total outputs
Attack Surface

ContentPen Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionadmin_initcontentpen-plugin.php:55
actionrest_api_initcontentpen-plugin.php:56
actionplugins_loadedcontentpen-plugin.php:123
actionadmin_enqueue_scriptsincludes\class-contentpen-admin.php:20
actionrest_api_initincludes\class-contentpen-api.php:23
actionadmin_menupage.php:20
actionadmin_enqueue_scriptspage.php:21
actionadmin_noticespage.php:22
Maintenance & Trust

ContentPen Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 18, 2026
PHP min version7.4
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs200
Developer Profile

ContentPen Developer Profile

contentpen

1 plugin · 200 total installs

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

How We Detect ContentPen

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/contentpen/assets/css/contentpen.css/wp-content/plugins/contentpen/assets/js/contentpen.js
Script Paths
/wp-content/plugins/contentpen/assets/js/contentpen.js
Version Parameters
contentpen/assets/css/contentpen.css?ver=contentpen/assets/js/contentpen.js?ver=

HTML / DOM Fingerprints

CSS Classes
contentpen-wrapcontentpen-boxcontentpen-logocontentpen-settings-formapi-key-status
Data Attributes
data-noncedata-api-endpoint
JS Globals
contentpenData
REST Endpoints
/wp-json/contentpen/v1
FAQ

Frequently Asked Questions about ContentPen