Target Visitors Security & Risk Analysis

wordpress.org/plugins/target-visitors

Plugin shows a special message to your blog's visitors, who coming from search engines (Google, Yandex, MSN, Yahoo, Mail.

10 active installs v1.2.5 PHP + WP 2.3.2+ Updated Unknown
googlesearch-enginesseotarget-visitorsyandex
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Target Visitors Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The 'target-visitors' v1.2.5 plugin exhibits a mixed security posture. On the positive side, the plugin has no recorded vulnerabilities (CVEs) and its static analysis reveals no obvious attack surface points like unprotected AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, all detected SQL queries utilize prepared statements, which is a significant good practice. However, a major concern arises from the output escaping, where 100% of detected outputs are not properly escaped. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected into the site. The taint analysis, while not flagging critical or high severity issues, did find three flows with unsanitized paths, which could potentially lead to path traversal or other file system-related vulnerabilities if exploited in conjunction with other weaknesses. The complete lack of nonce and capability checks on any entry points, although the entry points are currently zero, leaves a potential future risk if the plugin's functionality expands without proper security implementations. The absence of vulnerability history, while seemingly good, could also mean the plugin hasn't been subjected to extensive security testing or hasn't been widely used enough to attract vulnerability discovery. Overall, while the plugin currently lacks critical identified vulnerabilities and has a minimal attack surface, the prevalent lack of output escaping is a severe and immediate security concern.

Key Concerns

  • 100% of outputs are not properly escaped
  • 3 flows with unsanitized paths found
  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

Target Visitors Security Vulnerabilities

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

Target Visitors Code Analysis

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

Output Escaping

0% escaped6 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
target_visitors_options_page (wp-target-visitors.php:79)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Target Visitors Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_headwp-target-visitors.php:61
Maintenance & Trust

Target Visitors Maintenance & Trust

Maintenance Signals

WordPress version tested2.8
Last updatedUnknown
PHP min version
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Target Visitors Developer Profile

getincss

1 plugin · 10 total installs

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

How We Detect Target Visitors

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/target-visitors/target-visitors.css

HTML / DOM Fingerprints

CSS Classes
se_request
Shortcode Output
<div class="se_request"><a href="[PERMALINK]"><b>[SE_REQUEST]</b></a><a href="[RSS_URL]"><b>RSS</b></a>
FAQ

Frequently Asked Questions about Target Visitors