WP Gitlab Security & Risk Analysis

wordpress.org/plugins/wp-gitlab

Display users Gitlab public profile, repositories, commits, and issues.

10 active installs v1.0 PHP + WP 3.0.1+ Updated Apr 8, 2015
commitsgitlabissuesprofilerepositories
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Gitlab Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The wp-gitlab v1.0 plugin exhibits a mixed security posture. On the positive side, it demonstrates good practices by avoiding dangerous functions, using prepared statements for all SQL queries, and having no known vulnerabilities or CVEs in its history. The absence of external HTTP requests and a zero taint flow analysis also reduces potential attack vectors. However, several areas raise significant concerns. The lack of nonce checks and capability checks is a major weakness, especially given the presence of four shortcodes which act as entry points into the plugin. Furthermore, a very low percentage of properly escaped output (3%) suggests a high risk of cross-site scripting (XSS) vulnerabilities, where user-supplied data could be injected and executed in the browser of other users. While the attack surface is currently small and has no unprotected entry points, the absence of crucial security checks leaves it vulnerable to future exploits if new entry points are added or if the existing shortcodes are misused.

Key Concerns

  • No nonce checks on entry points
  • No capability checks on entry points
  • Very low percentage of properly escaped output
Vulnerabilities
None known

WP Gitlab Security Vulnerabilities

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

WP Gitlab Release Timeline

No version history available.
Code Analysis
Analyzed Mar 17, 2026

WP Gitlab Code Analysis

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

Output Escaping

3% escaped80 total outputs
Attack Surface

WP Gitlab Attack Surface

Entry Points4
Unprotected0

Shortcodes 4

[gitlab-profile] wp-gitlab.php:475
[gitlab-repos] wp-gitlab.php:508
[gitlab-commits] wp-gitlab.php:542
[gitlab-issues] wp-gitlab.php:576
WordPress Hooks 4
actionwp_enqueue_scriptswp-gitlab.php:16
actionadmin_menuwp-gitlab.php:28
actionadmin_initwp-gitlab.php:29
actionwidgets_initwp-gitlab.php:68
Maintenance & Trust

WP Gitlab Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedApr 8, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP Gitlab Developer Profile

CFarence

1 plugin · 10 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 Gitlab

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-gitlab/wp-gitlab.css

HTML / DOM Fingerprints

CSS Classes
wpgitlab-profilewpgitlab-userwpgitlab-usernamewpgitlab-namewpgitlab-bblockwpgitlab-countwpgitlab-text
Data Attributes
id="wpgitlab_cache_time"name="wpgitlab_cache_time"id="wpgitlab_clear_cache"name="wpgitlab_clear_cache"id="wpgitlab_url"name="wpgitlab_url"+2 more
FAQ

Frequently Asked Questions about WP Gitlab