image_src Security & Risk Analysis

wordpress.org/plugins/image-src

Add the "image_src" microformat.

10 active installs v1.0.0 PHP + WP 2.8.0+ Updated Feb 14, 2013
image_srcmicroformats
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is image_src Safe to Use in 2026?

Generally Safe

Score 85/100

image_src 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 "image-src" plugin version 1.0.0 exhibits a strong security posture based on the provided static analysis. There are no identified attack surface entry points, indicating that the plugin does not expose any direct interfaces like AJAX handlers, REST API routes, shortcodes, or cron events that could be exploited. Furthermore, the code analysis reveals no dangerous functions, raw SQL queries, file operations, or external HTTP requests. The absence of unsanitized taint flows and the use of prepared statements for all SQL queries are significant strengths.

However, there are areas for improvement. The plugin has a 50% rate of proper output escaping, meaning half of its outputs are not properly escaped, which could lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is ever rendered directly. Additionally, the complete absence of nonce checks and capability checks across all potential (though currently zero) entry points is concerning. While the attack surface is currently zero, if any entry points are added in the future, these checks would be crucial for preventing Cross-Site Request Forgery (CSRF) and unauthorized access.

The plugin has no recorded vulnerability history, which is a positive indicator of its current security. This, combined with the clean static analysis, suggests a generally safe plugin. However, the lack of basic security checks like nonces and capability checks on any potential future entry points represents a weakness that should be addressed proactively to maintain a robust security profile as the plugin evolves.

Key Concerns

  • Half of outputs are not properly escaped
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

image_src Security Vulnerabilities

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

image_src Code Analysis

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

Output Escaping

50% escaped2 total outputs
Attack Surface

image_src Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_headimage-src.php:12
Maintenance & Trust

image_src Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedFeb 14, 2013
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

image_src Developer Profile

ryanve

5 plugins · 50 total installs

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

How We Detect image_src

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
<link rel='image_src' href='
FAQ

Frequently Asked Questions about image_src