TweetPost Security & Risk Analysis

wordpress.org/plugins/tweetpost

Multi-user aware Twitter plugin adds a tweet button to posts and/or automatically tweets bit.ly or su.pr links to new posts.

10 active installs v1.3 PHP + WP 2.7+ Updated Sep 7, 2010
twittertwitter-integrationtwitter-poster
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is TweetPost Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 15yr ago
Risk Assessment

The "tweetpost" plugin v1.3 exhibits a mixed security posture. On the positive side, there are no known CVEs, and the plugin demonstrates good practices by using prepared statements for all SQL queries and including a capability check. However, significant concerns arise from the static analysis. The limited output escaping (15% properly escaped) indicates a high risk of cross-site scripting (XSS) vulnerabilities, as user-supplied data is likely being rendered without sufficient sanitization. Furthermore, the taint analysis reveals a flow with unsanitized paths, suggesting potential for arbitrary file access or manipulation, although the severity is not explicitly classified as critical or high in this report. The absence of nonce checks on AJAX handlers and REST API routes, coupled with a lack of reported vulnerabilities, might suggest a very small attack surface, but the identified taint flow and poor output escaping remain serious concerns that could be exploited if an attacker can introduce malicious data.

Key Concerns

  • Low percentage of properly escaped output
  • Taint flow with unsanitized paths
  • No nonce checks on AJAX/REST
Vulnerabilities
None known

TweetPost Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

TweetPost Release Timeline

v1.3Current
v1.2
v1.1
v1.0.1
v1.0
v0.8
v0.7
v0.5
v0.4
v0.3
v0.2
v0.1
Code Analysis
Analyzed Mar 17, 2026

TweetPost Code Analysis

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

Output Escaping

15% escaped13 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<account> (account.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

TweetPost Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 12
actionadmin_menutweetpost.php:116
actionadmin_inittweetpost.php:117
filterthe_contenttweetpost.php:431
actionshow_user_profiletweetpost.php:433
actionedit_user_profiletweetpost.php:434
actionpersonal_options_updatetweetpost.php:435
actionedit_user_profile_updatetweetpost.php:436
actionadmin_noticestweetpost.php:437
actionnew_to_publishtweetpost.php:438
actiondraft_to_publishtweetpost.php:439
actionpending_to_publishtweetpost.php:440
actionfuture_to_publishtweetpost.php:441
Maintenance & Trust

TweetPost Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedSep 7, 2010
PHP min version
Downloads8K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

TweetPost Developer Profile

Randy Hunt

4 plugins · 40 total installs

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

How We Detect TweetPost

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/tweetpost/tweetpost.js
Script Paths
/wp-content/plugins/tweetpost/tweetpost.js

HTML / DOM Fingerprints

CSS Classes
tweet_button
FAQ

Frequently Asked Questions about TweetPost