Jetpack Twitter Via Security & Risk Analysis

wordpress.org/plugins/jetpack-twitter-via

Adds 'via @username' to the Tweet Button provided in "Jetpack by WordPress.com"

20 active installs v1.0.0 PHP + WP 3.2+ Updated Nov 26, 2012
jetpacktwitter
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Jetpack Twitter Via Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The jetpack-twitter-via v1.0.0 plugin exhibits a strong security posture based on the provided static analysis. There are no identified entry points like AJAX handlers, REST API routes, or shortcodes that are exposed without authentication or permission checks. The code demonstrates good development practices by utilizing prepared statements for all SQL queries, properly escaping all output, and including nonce checks. The absence of dangerous functions, file operations, external HTTP requests, and known vulnerabilities further reinforces its security.

However, a notable absence is the lack of capability checks on any of its functions. While the static analysis reports no direct vulnerabilities, this omission could potentially lead to privilege escalation issues if any functionalities were to be introduced or were implicitly accessible without proper authorization. The plugin's vulnerability history is clean, suggesting a history of secure development or limited exposure. Overall, this plugin appears to be developed with security in mind, but the missing capability checks represent a potential area for improvement and a minor weakness in its security model.

Key Concerns

  • Missing capability checks
Vulnerabilities
None known

Jetpack Twitter Via Security Vulnerabilities

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

Jetpack Twitter Via Release Timeline

v1.0.0Current
Code Analysis
Analyzed Mar 16, 2026

Jetpack Twitter Via Code Analysis

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

Output Escaping

100% escaped2 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
jtv_settings_validate (jetpack-twitter-via.php:88)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Jetpack Twitter Via Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
filterjetpack_sharing_twitter_viajetpack-twitter-via.php:30
actionadmin_initjetpack-twitter-via.php:47
actionsharing_global_optionsjetpack-twitter-via.php:61
actionsharing_admin_updatejetpack-twitter-via.php:93
Maintenance & Trust

Jetpack Twitter Via Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedNov 26, 2012
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings3
Active installs20
Developer Profile

Jetpack Twitter Via Developer Profile

Konstantin Obenland

13 plugins · 23K total installs

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

How We Detect Jetpack Twitter Via

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
description
HTML Comments
End of file jetpack-twitter-via.phpLocation: ./wp-content/plugins/jetpack-twitter-via/jetpack-twitter-via.php
Data Attributes
id="jtv-jetpack-twitter-via"name="jtv-jetpack-twitter-via"id="jtv-jetpack-twitter-via"name="jtv-jetpack-twitter-via"id="jtv-jetpack-twitter-via"name="jtv-jetpack-twitter-via"+5 more
FAQ

Frequently Asked Questions about Jetpack Twitter Via