Private Password Posts Security & Risk Analysis

wordpress.org/plugins/private-password-posts

Hide private posts and password protected posts in front end

10 active installs v1.5.0 PHP + WP 3.2+ Updated Unknown
accesspassword-postpassword-protect-postprivate-posttheme
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Private Password Posts Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "private-password-posts" v1.5.0 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the attack surface. Furthermore, the code demonstrates good practices by not using dangerous functions, performing file operations, or making external HTTP requests. All SQL queries are prepared, and there are no recorded vulnerabilities in its history, suggesting a well-maintained and secure plugin.

However, there are a few areas of concern. The taint analysis identified two flows with unsanitized paths, which, while not classified as critical or high severity in this analysis, represent a potential risk if user-supplied data can influence these paths. Additionally, while the total number of outputs is small, 40% of them are not properly escaped. This could lead to cross-site scripting (XSS) vulnerabilities if the data being output is untrusted and not adequately sanitized before display.

Overall, the plugin is robust due to its limited attack surface and lack of historical vulnerabilities. The main weaknesses lie in the identified unsanitized paths and the lack of complete output escaping, which, if exploited, could lead to security issues.

Key Concerns

  • Taint flows with unsanitized paths found
  • Untrusted output not properly escaped (40%)
Vulnerabilities
None known

Private Password Posts Security Vulnerabilities

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

Private Password Posts Code Analysis

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

Output Escaping

60% escaped5 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
tomas_private_posts_menu_setting (private-password-posts.php:72)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Private Password Posts Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
filterposts_whereprivate-password-posts.php:30
filterposts_whereprivate-password-posts.php:41
filterposts_whereprivate-password-posts.php:42
filterthe_password_formprivate-password-posts.php:61
actionadmin_menuprivate-password-posts.php:69
Maintenance & Trust

Private Password Posts Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedUnknown
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Private Password Posts Developer Profile

Tomas

10 plugins · 7K total installs

72
trust score
Avg Security Score
90/100
Avg Patch Time
526 days
View full developer profile
Detection Fingerprints

How We Detect Private Password Posts

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
post-password-form
HTML Comments
Copyright 2016 - 2022 Tomas Zhu This program comes with ABSOLUTELY NO WARRANTY;1.4.01.5.2+2 more
Data Attributes
id="bpmoform"name="bpmoform"id="bpmotable"id="tomas_word_private_password_posts_sbumit"name="tomas_word_private_password_posts_sbumit"
FAQ

Frequently Asked Questions about Private Password Posts