Content Permissions for Pages & Posts Security & Risk Analysis

wordpress.org/plugins/content-permissions-for-pages-posts

Control your content permissions with simple shortcode. Restrict content access to members,guests or logged in one's.

10 active installs v1.0 PHP + WP 3.0+ Updated Nov 17, 2017
content-permissionsmembersprivate-contentrestrict-contentrestrict-guest
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Content Permissions for Pages & Posts Safe to Use in 2026?

Generally Safe

Score 85/100

Content Permissions for Pages & Posts has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The "content-permissions-for-pages-posts" v1.0 plugin exhibits a strong security posture based on the provided static analysis and vulnerability history. The absence of dangerous functions, the consistent use of prepared statements for SQL queries, and the proper escaping of all output are significant strengths. The plugin also has no recorded vulnerabilities, suggesting a history of secure development or a lack of past exposure.

However, the analysis does highlight a few areas that could be improved. The presence of two shortcodes without explicit mention of capability checks or nonce verification is a potential concern, as these could represent entry points if not properly secured within their implementation. While no taint flows with unsanitized paths were detected, the lack of any observed taint flows might also indicate that the static analysis engine had limited visibility or that the plugin's functionality is very basic, which can sometimes hide vulnerabilities.

In conclusion, the plugin appears to be relatively secure, with good practices in place for SQL and output handling. The main area for attention is ensuring that the shortcode implementations are robustly secured against potential misuse. The clean vulnerability history is reassuring, but continuous vigilance and thorough code review are always recommended for any plugin.

Key Concerns

  • Potential shortcode vulnerabilities
  • Lack of nonce checks
  • Lack of capability checks
Vulnerabilities
None known

Content Permissions for Pages & Posts Security Vulnerabilities

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

Content Permissions for Pages & Posts Release Timeline

No version history available.
Code Analysis
Analyzed Mar 17, 2026

Content Permissions for Pages & Posts Code Analysis

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

Content Permissions for Pages & Posts Attack Surface

Entry Points2
Unprotected0

Shortcodes 2

[cpp_guests] index.php:17
[cpp_users] index.php:32
Maintenance & Trust

Content Permissions for Pages & Posts Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedNov 17, 2017
PHP min version
Downloads1K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Content Permissions for Pages & Posts Developer Profile

param

3 plugins · 1K total installs

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

How We Detect Content Permissions for Pages & Posts

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/content-permissions-for-pages-posts/

HTML / DOM Fingerprints

Shortcode Output
[cpp_guests][cpp_users]
FAQ

Frequently Asked Questions about Content Permissions for Pages & Posts