User Specific Posts Security & Risk Analysis

wordpress.org/plugins/user-specific-posts

Restrict any page/post visibility to a specific user only.

40 active installs v1.0.3 PHP 7.3+ WP 5.0+ Updated Apr 12, 2025
post-restrictionspecific-useruser-posts
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is User Specific Posts Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 11mo ago
Risk Assessment

The user-specific-posts plugin v1.0.3 demonstrates a strong security posture based on the provided static analysis. The code adheres to several best practices, including the absence of dangerous functions and external HTTP requests, and all SQL queries utilize prepared statements. Importantly, all identified outputs are properly escaped, and the plugin incorporates both nonce and capability checks for its entry points. The attack surface is minimal, consisting of a single shortcode, and notably, there are no unprotected entry points. This indicates a conscientious effort by the developers to secure the plugin.

Furthermore, the vulnerability history is exceptionally clean, with zero recorded CVEs of any severity. This pattern suggests a consistent focus on security by the development team or a lack of targeting by attackers. The taint analysis also shows no critical or high severity flows, reinforcing the perception of a secure codebase. While the static analysis didn't uncover any immediate exploitable flaws, the small attack surface and robust implementation are key strengths.

Overall, the plugin appears to be very secure. The absence of any reported vulnerabilities or concerning code patterns in the static analysis suggests a low risk of compromise. The developers have implemented appropriate security measures like prepared statements, output escaping, and authorization checks. The only potential area for minor concern, if any, would be the inherent complexity of shortcodes which can sometimes introduce subtle issues, but in this case, it is presented as a single, likely well-handled, entry point.

Vulnerabilities
None known

User Specific Posts Security Vulnerabilities

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

User Specific Posts Code Analysis

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

Output Escaping

100% escaped1 total outputs
Attack Surface

User Specific Posts Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[usp_posts] user_specific_posts.php:24
WordPress Hooks 3
actionadd_meta_boxesuser_specific_posts.php:21
actionsave_postuser_specific_posts.php:22
actiontemplate_redirectuser_specific_posts.php:23
Maintenance & Trust

User Specific Posts Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedApr 12, 2025
PHP min version7.3
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs40
Developer Profile

User Specific Posts Developer Profile

mansurahamed

4 plugins · 290 total installs

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

How We Detect User Specific Posts

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/user-specific-posts/user-specific-posts.php

HTML / DOM Fingerprints

CSS Classes
entry-headerentry-titleentry-content
HTML Comments
<!-- THIS IS WHERE THE FUN PART GOES -->
Data Attributes
name="usp_user_id"id="post-class="
Shortcode Output
<article id="post-<header class="entry-header"><h1 class="entry-title"><a href="<div class="entry-content">
FAQ

Frequently Asked Questions about User Specific Posts