Git it Write – Write posts from GitHub Security & Risk Analysis

wordpress.org/plugins/git-it-write

Publish markdown files present in a GitHub repository as posts to WordPress automatically

100 active installs v2.0 PHP 5.3+ WP 4.4+ Updated Aug 3, 2024
editorgithubmarkdownpostspublish
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Git it Write – Write posts from GitHub Safe to Use in 2026?

Generally Safe

Score 92/100

Git it Write – Write posts from GitHub has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "git-it-write" v2.0 plugin exhibits a generally strong security posture based on the provided static analysis. A significant positive is the absence of known vulnerabilities and CVEs, coupled with the fact that all SQL queries utilize prepared statements, indicating good database interaction practices. The high percentage of properly escaped outputs further suggests an effort to mitigate cross-site scripting (XSS) risks. However, there are areas for concern. The lack of capability checks on any entry points, including the single REST API route and shortcode, represents a critical oversight. While the attack surface is small and no AJAX handlers are exposed without authentication, the absence of proper authorization checks on the existing entry points leaves them vulnerable to unauthorized access and manipulation if an attacker can bypass authentication or exploit other system vulnerabilities. The lack of any taint analysis results is unusual and might indicate that the analysis tool was not able to perform this critical function effectively on this plugin's code, or that the code is extremely simple. In conclusion, while the plugin benefits from a clean vulnerability history and good practices in SQL and output handling, the absence of capability checks is a significant weakness that elevates its risk profile.

Key Concerns

  • No capability checks on entry points
  • No taint analysis performed
Vulnerabilities
None known

Git it Write – Write posts from GitHub Security Vulnerabilities

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

Git it Write – Write posts from GitHub Code Analysis

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

Output Escaping

96% escaped46 total outputs
Attack Surface

Git it Write – Write posts from GitHub Attack Surface

Entry Points2
Unprotected0

REST API Routes 1

POST/wp-json/giw/v1/publishincludes\webhook.php:10

Shortcodes 1

[giw_edit_link] includes\shortcodes.php:9
WordPress Hooks 3
actionadmin_menuadmin\admin.php:11
actionadmin_enqueue_scriptsadmin\admin.php:13
actionrest_api_initincludes\webhook.php:9
Maintenance & Trust

Git it Write – Write posts from GitHub Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedAug 3, 2024
PHP min version5.3
Downloads7K

Community Trust

Rating94/100
Number of ratings7
Active installs100
Developer Profile

Git it Write – Write posts from GitHub Developer Profile

vaakash

6 plugins · 133K total installs

76
trust score
Avg Security Score
96/100
Avg Patch Time
157 days
View full developer profile
Detection Fingerprints

How We Detect Git it Write – Write posts from GitHub

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/git-it-write/admin/css/style.css/wp-content/plugins/git-it-write/admin/js/script.js
Script Paths
/wp-content/plugins/git-it-write/admin/js/script.js
Version Parameters
git-it-write/admin/css/style.css?ver=git-it-write/admin/js/script.js?ver=

HTML / DOM Fingerprints

CSS Classes
giw_titletitle-count
Data Attributes
data-giw-id
FAQ

Frequently Asked Questions about Git it Write – Write posts from GitHub