Tweets Widget Security & Risk Analysis

wordpress.org/plugins/tweets-widget

Tweets Widget compatible with the new Twitter API 1.1

20 active installs v1.0 PHP + WP 3.5.1+ Updated Aug 29, 2016
loklakloklak-apioauthtweetstwitter
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Tweets Widget Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

The "tweets-widget" v1.0 plugin exhibits a generally good security posture due to the absence of known vulnerabilities and the use of prepared statements for all SQL queries. The limited attack surface, consisting solely of a single shortcode, also contributes positively. However, significant concerns arise from the lack of input validation and output escaping, with only 25% of outputs being properly escaped. The absence of nonce checks and capability checks for any potential entry points, even though there are none identified as unprotected in the static analysis, leaves room for future vulnerabilities if the plugin's functionality expands or is misused. The plugin also performs file operations and external HTTP requests, which can be points of weakness if not handled securely. The clean vulnerability history is a strength, suggesting a proactive approach to security from the developer or a lack of discovered issues. Despite these strengths, the insufficient output escaping is a notable weakness that could lead to cross-site scripting (XSS) vulnerabilities.

Key Concerns

  • Insufficient output escaping
  • No nonce checks on entry points
  • No capability checks on entry points
  • File operations without specific checks noted
  • External HTTP requests without specific checks noted
Vulnerabilities
None known

Tweets Widget Security Vulnerabilities

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

Tweets Widget Code Analysis

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

Output Escaping

25% escaped20 total outputs
Attack Surface

Tweets Widget Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[tweets] tweets.php:345
WordPress Hooks 5
filterplugin_localeapi\wp-twitter-api\twitter-api.php:177
actionadmin_initloklak_php_api\Lib\loklak-api-admin.php:2
actionplugins_loadedloklak_php_api\Lib\loklak-api-admin.php:71
actionadmin_enqueue_scriptsloklak_php_api\Lib\loklak-api-admin.php:72
actionwidgets_inittweets.php:335
Maintenance & Trust

Tweets Widget Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedAug 29, 2016
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

Tweets Widget Developer Profile

fossasia

2 plugins · 30 total installs

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

How We Detect Tweets Widget

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/tweets-widget/api/wp-twitter-api/twitter-api.php/wp-content/plugins/tweets-widget/loklak_php_api/loklak.php

HTML / DOM Fingerprints

CSS Classes
tweet-texttweet-details
FAQ

Frequently Asked Questions about Tweets Widget