Subscribers Only Content Security & Risk Analysis

wordpress.org/plugins/subscribers-only-content

Allows blog admin to set specific pages and posts to only be visible to users with the 'read' capability.

20 active installs v1.0.1 PHP + WP 2.5+ Updated Jun 13, 2010
filter-contentmemberssubscribers
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Subscribers Only Content Safe to Use in 2026?

Generally Safe

Score 85/100

Subscribers Only Content 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 'subscribers-only-content' v1.0.1 plugin exhibits a very strong security posture based on the provided static analysis. The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events as entry points significantly limits the potential attack surface. Furthermore, the code signals indicate robust security practices, with all SQL queries using prepared statements, all outputs being properly escaped, and the presence of nonce and capability checks. The lack of any critical or high-severity taint flows further reinforces this positive assessment.

The vulnerability history shows no known CVEs, which is an excellent sign for this plugin's security. The absence of any recorded vulnerabilities suggests a mature and well-maintained codebase. While the static analysis found no direct security flaws, it's important to remember that static analysis has limitations and cannot detect all types of vulnerabilities, especially those that might arise from complex interactions with other plugins or themes, or environment-specific issues.

In conclusion, 'subscribers-only-content' v1.0.1 appears to be a highly secure plugin. Its minimal attack surface and strong adherence to secure coding practices are commendable. The lack of vulnerability history is a significant strength. However, continuous monitoring and updates are always recommended for any software to maintain its security against evolving threats.

Vulnerabilities
None known

Subscribers Only Content Security Vulnerabilities

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

Subscribers Only Content Code Analysis

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

Subscribers Only Content Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_menusubscribers-only-content.php:159
actionsave_postsubscribers-only-content.php:160
actionsave_pagesubscribers-only-content.php:161
filterposts_wheresubscribers-only-content.php:162
filterposts_joinsubscribers-only-content.php:163
filterget_pagessubscribers-only-content.php:164
Maintenance & Trust

Subscribers Only Content Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedJun 13, 2010
PHP min version
Downloads6K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

Subscribers Only Content Developer Profile

prettyboymp

4 plugins · 50 total installs

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

How We Detect Subscribers Only Content

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
chk_subscribers_onlyid="chk_subscribers_only"id="subscribers_only_nonce"
FAQ

Frequently Asked Questions about Subscribers Only Content