Crossposterous Security & Risk Analysis

wordpress.org/plugins/crossposterous

WordPress to Posterous cross-posting plugin.

10 active installs v1.2.1 PHP + WP 2.7+ Updated Nov 9, 2010
crosspostposterousposts
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Crossposterous Safe to Use in 2026?

Generally Safe

Score 85/100

Crossposterous 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 plugin "crossposterous" v1.2.1 exhibits a seemingly strong security posture based on the static analysis, with no identified attack surface points like AJAX handlers, REST API routes, shortcodes, or cron events that are exposed without authentication or permission checks. The code also demonstrates good practices regarding SQL queries, using prepared statements exclusively, and no known vulnerabilities (CVEs) are recorded. This suggests a plugin that has been developed with security in mind and has a clean history.

However, the static analysis reveals significant concerns regarding output escaping. With 4 total outputs and 0% properly escaped, this represents a critical weakness. Any data displayed by the plugin that originates from user input or external sources could be vulnerable to Cross-Site Scripting (XSS) attacks, allowing attackers to inject malicious scripts into the user's browser. While the plugin doesn't appear to use dangerous functions, execute file operations, or make external HTTP requests in a way that seems immediately exploitable, the complete lack of output escaping is a substantial security risk. The absence of nonce checks and capability checks on potential (though currently unlisted) entry points further contributes to a potential for privilege escalation or unauthorized actions if any such points were to be discovered or added in future versions.

In conclusion, while "crossposterous" v1.2.1 shines in its lack of known vulnerabilities and its use of prepared statements, the critical deficiency in output escaping presents a substantial risk. The plugin's attack surface appears minimal in its current state, but the unescaped output is a glaring security flaw that needs immediate attention. The clean vulnerability history is positive, but it does not mitigate the present risks identified through static analysis.

Key Concerns

  • Unescaped output detected
  • No nonce checks identified
  • No capability checks identified
Vulnerabilities
None known

Crossposterous Security Vulnerabilities

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

Crossposterous Release Timeline

v1.2.1Current
v1.2
v1.1
v1.0
Code Analysis
Analyzed Mar 17, 2026

Crossposterous Code Analysis

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

Output Escaping

0% escaped4 total outputs
Attack Surface

Crossposterous Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionadmin_menucrossposterous.php:44
actionadmin_initcrossposterous.php:45
filterplugin_row_metacrossposterous.php:46
actionnew_to_publishcrossposterous.php:232
actiondraft_to_publishcrossposterous.php:233
actionfuture_to_publishcrossposterous.php:234
actionpending_to_publishcrossposterous.php:235
Maintenance & Trust

Crossposterous Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedNov 9, 2010
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Crossposterous 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 Crossposterous

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
wrapicon32button-primary
Data Attributes
id="posterous_email"name="crossposterous[posterous_email]"id="posterous_password"name="crossposterous[posterous_password]"id="posterous_site"name="crossposterous[siteid]"+1 more
REST Endpoints
http://posterous.com/api/getsiteshttp://posterous.com/api/newpost
FAQ

Frequently Asked Questions about Crossposterous