Custom Shortlink Domain Security & Risk Analysis

wordpress.org/plugins/shortlink-domain

Customise the domain name used to generate shortlink URLs.

10 active installs v0.1.3 PHP + WP 3.3.1+ Updated Apr 28, 2012
customdomainshortenershortlinkurl
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Custom Shortlink Domain Safe to Use in 2026?

Generally Safe

Score 85/100

Custom Shortlink Domain 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 "shortlink-domain" plugin v0.1.3 demonstrates a generally strong security posture based on the static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits its attack surface, and crucially, there are no entry points found without proper authentication checks. The code also shows a commitment to security by exclusively using prepared statements for its SQL queries. However, the analysis does reveal a critical weakness: 100% of its output is not properly escaped. This means that any data displayed by the plugin could potentially be vulnerable to Cross-Site Scripting (XSS) attacks if that data originates from user input or other untrusted sources.

The vulnerability history is clean, with no known CVEs recorded for this plugin. This is a positive indicator, suggesting that the plugin's developers have a good track record or that the plugin is not a frequent target. However, the lack of any recorded vulnerabilities should not be interpreted as an absolute guarantee of future safety, especially given the identified output escaping issue. The clean history, coupled with the missing output escaping, suggests that while the plugin might not have been historically exploited for its vulnerabilities, the potential for XSS remains a significant concern.

In conclusion, "shortlink-domain" v0.1.3 exhibits a small attack surface and responsible SQL handling, which are commendable. Nevertheless, the complete lack of output escaping represents a serious security deficiency that could expose the WordPress site to XSS vulnerabilities. While the plugin has no known vulnerabilities, this specific coding practice warrants immediate attention and remediation.

Key Concerns

  • Output is not properly escaped
Vulnerabilities
None known

Custom Shortlink Domain Security Vulnerabilities

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

Custom Shortlink Domain Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

Custom Shortlink Domain Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
filterget_shortlinkindex.php:41
actionadmin_initindex.php:43
Maintenance & Trust

Custom Shortlink Domain Maintenance & Trust

Maintenance Signals

WordPress version tested3.3.2
Last updatedApr 28, 2012
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Custom Shortlink Domain Developer Profile

Steve

4 plugins · 3K total installs

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

How We Detect Custom Shortlink Domain

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
regular-textcode
Data Attributes
name="shortlink_domain"id="shortlink_domain"
FAQ

Frequently Asked Questions about Custom Shortlink Domain