Gravity Forms Enhancements Security & Risk Analysis

wordpress.org/plugins/gravity-forms-enhancements

Simple library to enhance the Gravity Forms experience, build on a necessity and desire not to amend Gravity Forms core files.

10 active installs v1.3.5 PHP + WP 3.3+ Updated Mar 15, 2015
gravity-formsgravity-forms-labelsgravity-forms-placeholdershtml5-placeholders
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Gravity Forms Enhancements Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The "gravity-forms-enhancements" plugin v1.3.5 exhibits a seemingly strong security posture based on the provided static analysis. The absence of identified entry points like AJAX handlers, REST API routes, shortcodes, and cron events suggests a minimal attack surface. Furthermore, the code signals indicate robust output escaping and a lack of dangerous functions, file operations, or external HTTP requests. The vulnerability history is also clean, with no recorded CVEs, which is a positive indicator.

However, a significant concern arises from the single SQL query that is not using prepared statements. This represents a direct risk of SQL injection, even if the attack surface is small. The complete absence of nonce and capability checks, coupled with the fact that no AJAX handlers or REST API routes were found (suggesting these might not be part of the plugin's functionality), points to a potential lack of built-in security mechanisms for any future or undiscovered entry points. While the current data is reassuring in many aspects, the unescaped SQL query is a critical vulnerability that requires immediate attention.

In conclusion, while the plugin appears to follow good security practices in output escaping and avoids common pitfalls, the single unescaped SQL query significantly lowers its overall security rating. The lack of identified entry points and vulnerability history is a strength, but the presence of even one raw SQL query without proper preparation is a major weakness that needs to be addressed to mitigate the risk of SQL injection.

Key Concerns

  • SQL query not using prepared statements
Vulnerabilities
None known

Gravity Forms Enhancements Security Vulnerabilities

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

Gravity Forms Enhancements Code Analysis

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

SQL Query Safety

0% prepared1 total queries
Attack Surface

Gravity Forms Enhancements Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionplugins_loadedGravityFormsEnhacnerInit.php:46
Maintenance & Trust

Gravity Forms Enhancements Maintenance & Trust

Maintenance Signals

WordPress version tested4.4.34
Last updatedMar 15, 2015
PHP min version
Downloads2K

Community Trust

Rating88/100
Number of ratings7
Active installs10
Developer Profile

Gravity Forms Enhancements Developer Profile

latorante

2 plugins · 30 total installs

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

How We Detect Gravity Forms Enhancements

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/gravity-forms-enhancements/css/main.css/wp-content/plugins/gravity-forms-enhancements/js/gravity-forms-enhancer.js
Script Paths
/wp-content/plugins/gravity-forms-enhancements/js/gravity-forms-enhancer.js
Version Parameters
gravity-forms-enhancements/css/main.css?ver=gravity-forms-enhancements/js/gravity-forms-enhancer.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Gravity Forms Enhancements