WP-jTweets Security & Risk Analysis

wordpress.org/plugins/wp-jtweets

A widget that uses jQuery and Twitter to display a user's tweets (or can just list the updates). Works with the Twitter API 1.1

10 active installs v1.1.5 PHP + WP 3.2+ Updated Feb 26, 2021
feedjsonrotatetweetstwitter
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP-jTweets Safe to Use in 2026?

Generally Safe

Score 85/100

WP-jTweets 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 wp-jtweets plugin v1.1.5 exhibits a generally good security posture based on the static analysis. The absence of known CVEs, combined with the fact that all SQL queries use prepared statements, suggests a proactive approach to security and a clean history. The plugin also appears to have a very limited attack surface with zero identified entry points like AJAX handlers, REST API routes, or shortcodes. However, a significant concern is the low percentage (32%) of properly escaped output. This indicates a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, where user-supplied data could be injected and executed in the browser. Furthermore, the plugin performs file operations and makes external HTTP requests without any observable capability checks or nonce checks, which could potentially be exploited if these operations involve user-controlled data or are triggered in an unauthorized manner. The lack of any taint analysis results suggests either no data flows were analyzed or none were found to be problematic, but this should not overshadow the identified output escaping and authorization concerns.

Key Concerns

  • Low output escaping percentage (32%)
  • File operations without capability checks
  • External HTTP requests without capability checks
  • File operations without nonce checks
  • External HTTP requests without nonce checks
Vulnerabilities
None known

WP-jTweets Security Vulnerabilities

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

WP-jTweets Code Analysis

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

Output Escaping

32% escaped102 total outputs
Attack Surface

WP-jTweets Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_enqueue_scriptsindex.php:36
actionwidgets_initindex.php:41
Maintenance & Trust

WP-jTweets Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.0
Last updatedFeb 26, 2021
PHP min version
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP-jTweets Developer Profile

Aaron Reimann

4 plugins · 10K total installs

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

How We Detect WP-jTweets

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-jtweets/style.css/wp-content/plugins/wp-jtweets/js/jtweets.js
Script Paths
/wp-content/plugins/wp-jtweets/js/jtweets.js
Version Parameters
wp-jtweets/style.css?ver=wp-jtweets/js/jtweets.js?ver=

HTML / DOM Fingerprints

CSS Classes
jtweets-feedjtweets-avatar-blockjtweets-avatar-block-1jtweets-avatar-block-2
Data Attributes
data-rotatetime
FAQ

Frequently Asked Questions about WP-jTweets