hRecipe Security & Risk Analysis

wordpress.org/plugins/hrecipe

Use hRecipe for creating Google Rich Snippets, for leveraging SEO results, and for attractively displaying your recipes.

70 active installs v0.6.1 PHP + WP 3.0+ Updated Nov 25, 2011
editorhrecipereciperecipe-seorecipes
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is hRecipe Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 14yr ago
Risk Assessment

The "hrecipe" plugin v0.6.1 presents a mixed security profile. On one hand, the static analysis reveals an extremely small attack surface with no apparent AJAX handlers, REST API routes, shortcodes, or cron events exposed. Furthermore, there are no detected dangerous functions, file operations, external HTTP requests, or taint flows, which are all positive indicators. The plugin also demonstrates good practices by exclusively using prepared statements for its SQL queries. However, a significant concern is the alarmingly low percentage (4%) of properly escaped output. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed within the WordPress site. The absence of capability checks and nonce checks on its (zero) entry points, while seemingly benign due to the lack of entry points, leaves a potential gap if any entry points were to be introduced or discovered later without these security measures.

Key Concerns

  • Low output escaping percentage
  • No capability checks
  • No nonce checks
Vulnerabilities
None known

hRecipe Security Vulnerabilities

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

hRecipe Release Timeline

v0.6.1Current
v0.6.0
v0.5.9.1
v0.5.9.0
v0.5.8.5
v0.5.8.4
v0.5.8.3
v0.5.8.2
v0.5.8.1
v0.5.8
v0.5.7.1
v0.5.7
v0.5.6
v0.5.5
v0.5.4.5
v0.5.4.4
v0.5.4.3
v0.5.4.2
v0.5.4.1
v0.5.4
Code Analysis
Analyzed Mar 16, 2026

hRecipe Code Analysis

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

Bundled Libraries

TinyMCE

Output Escaping

4% escaped28 total outputs
Attack Surface

hRecipe Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
filtermce_external_pluginshrecipe.class.php:37
filtermce_buttons_3hrecipe.class.php:38
filterplugin_action_linkshrecipe.php:61
actionwp_print_styleshrecipe.php:64
actioninithrecipe.php:66
actionadmin_inithrecipe.php:67
actionadmin_inithrecipe.php:68
actionadmin_menuhrecipe.php:69
actionmedia_upload_hrecipehrecipe.php:95
Maintenance & Trust

hRecipe Maintenance & Trust

Maintenance Signals

WordPress version tested3.3.2
Last updatedNov 25, 2011
PHP min version
Downloads25K

Community Trust

Rating94/100
Number of ratings3
Active installs70
Developer Profile

hRecipe Developer Profile

Dave Doolin

3 plugins · 90 total installs

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

How We Detect hRecipe

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/hrecipe/css/hrecipe.css/wp-content/plugins/hrecipe/css/hrecipe-editor.css/wp-content/plugins/hrecipe/css/hrecipe-options.css/wp-content/plugins/hrecipe/js/hrecipe_format.js/wp-content/plugins/hrecipe/js/hrecipe_launch.js/wp-content/plugins/hrecipe/js/hrecipescript.js
Script Paths
http://www.recip.ly/static/js/jquery-reciply.js

HTML / DOM Fingerprints

CSS Classes
hrecipehrecipe-editorhrecipe-optionshrecipe-bodyhrecipe-ingredientshrecipe-instructionshrecipe-preamblehrecipe-nutrition
HTML Comments
<!-- Testing...!!!! -->
Data Attributes
data-hrecipe-json
JS Globals
hRecipehRecipe_JSON_data
Shortcode Output
[hrecipe][/hrecipe][hrecipe-ingredients][/hrecipe-ingredients]
FAQ

Frequently Asked Questions about hRecipe