LAPDI Facepile Security & Risk Analysis

wordpress.org/plugins/tsp-facepile

Facepile allows you to add WordPress users photo icons to your blog's website in grid format.

10 active installs v1.1.6 PHP + WP 3.5.1+ Updated Feb 8, 2021
displayfaceslistmemberstiles
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is LAPDI Facepile Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The tsp-facepile plugin v1.1.6 presents a generally good security posture with no identified vulnerabilities in its history and a limited attack surface. The static analysis reveals no critical findings such as dangerous functions, file operations, or external HTTP requests. Taint analysis also shows no concerning flows. However, there are areas for improvement that slightly detract from an otherwise positive assessment. Specifically, the plugin's handling of SQL queries and output escaping raises concerns. While some SQL queries are prepared, a significant portion are not, and critically, none of the identified output operations are properly escaped. This lack of output escaping could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is ever incorporated into the plugin's output. The presence of a nonce check and a capability check for the shortcode are positive indicators of security awareness, but the absence of capability checks on other potential entry points like AJAX and REST API routes (though currently zero) is a minor weakness. Given the absence of known vulnerabilities and critical static analysis findings, the overall risk is currently low, but the unescaped output and partial SQL preparation warrant attention.

Key Concerns

  • Output escaping: 0% properly escaped
  • SQL queries: 50% not using prepared statements
  • Capability checks: 0 on entry points
Vulnerabilities
None known

LAPDI Facepile Security Vulnerabilities

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

LAPDI Facepile Code Analysis

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

SQL Query Safety

50% prepared2 total queries

Output Escaping

0% escaped1 total outputs
Attack Surface

LAPDI Facepile Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[tsp_facepile] tsp-facepile.php:56
WordPress Hooks 1
actionwidgets_inittsp-facepile.php:61
Maintenance & Trust

LAPDI Facepile Maintenance & Trust

Maintenance Signals

WordPress version tested5.6.17
Last updatedFeb 8, 2021
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

LAPDI Facepile Developer Profile

Sharron Denice

7 plugins · 220 total installs

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

How We Detect LAPDI Facepile

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/tsp-facepile/tsp-facepile.css

HTML / DOM Fingerprints

CSS Classes
tsp-facepile
Data Attributes
tsp-facepile-nonce-name
FAQ

Frequently Asked Questions about LAPDI Facepile