SF Generate Tags Security & Risk Analysis

wordpress.org/plugins/sf-generate-tags

Generate tags for posts from images or/and post text.

20 active installs v1.4.1 PHP + WP 3.8+ Updated Mar 23, 2018
editgenerateimagespoststags
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is SF Generate Tags Safe to Use in 2026?

Generally Safe

Score 85/100

SF Generate Tags has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The sf-generate-tags plugin v1.4.1 exhibits a concerning security posture due to a critical lack of proper input validation and authorization. While the plugin boasts no known vulnerabilities in its history and utilizes prepared statements for its SQL queries, this is overshadowed by significant risks identified in the static analysis. The presence of an unprotected AJAX handler represents a direct entry point for potential attacks, as there are no nonces or capability checks in place. Furthermore, the complete absence of output escaping for any identified outputs means that any data processed through these AJAX handlers could be susceptible to cross-site scripting (XSS) vulnerabilities, even if the data itself is not directly user-provided.

Despite the absence of dangerous functions, file operations, or external HTTP requests, and a clean vulnerability history suggesting diligent patching or a lack of past issues, the current implementation is far from secure. The 100% unescaped output and the unprotected AJAX handler are major red flags. The lack of any recorded vulnerabilities could be interpreted positively, but it's also possible that these weaknesses have simply not been exploited or discovered yet. The plugin needs immediate attention to address the unprotected AJAX endpoint and implement robust output escaping to mitigate XSS risks.

Key Concerns

  • Unprotected AJAX handler found
  • No output escaping implemented
  • No nonce checks on AJAX handlers
  • No capability checks on AJAX handlers
Vulnerabilities
None known

SF Generate Tags Security Vulnerabilities

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

SF Generate Tags 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
1 unprotected

SF Generate Tags Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_sf_generate_tagssf-tags.php:126
WordPress Hooks 4
actionadd_meta_boxessf-tags-admin.php:8
actionplugins_loadedsf-tags.php:22
actionwp_enqueue_scriptsf-tags.php:28
actionadmin_footersf-tags.php:64
Maintenance & Trust

SF Generate Tags Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedMar 23, 2018
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings3
Active installs20
Developer Profile

SF Generate Tags Developer Profile

Studiofreya

3 plugins · 50 total installs

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

How We Detect SF Generate Tags

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

Asset Fingerprints

Script Paths
/wp-content/plugins/sf-generate-tags/sf-tags-admin.php/wp-content/plugins/sf-generate-tags/sf-tags-filter-english.php

HTML / DOM Fingerprints

CSS Classes
sf-generate-tags-form
Data Attributes
id="sf_from_images"id="sf_from_text"id="sf_post_id"id="sf_limit_tags"id="btnSubmit"id="sf_remove_words"+1 more
JS Globals
window.ajaxurl
REST Endpoints
wp-json/sf-generate-tags
FAQ

Frequently Asked Questions about SF Generate Tags