Eloquent Security & Risk Analysis

wordpress.org/plugins/eloquent

Eloquent is an awesome front-end editor for your website.

10 active installs v0.2 PHP + WP 3.0.1+ Updated May 19, 2022
editoreloquentfront-endfrontendlive
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Eloquent Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 3yr ago
Risk Assessment

The 'eloquent' plugin v0.2 demonstrates a generally good security posture, with a notable absence of critical or high-severity code signals and a clean vulnerability history. The plugin shows strong adherence to secure coding practices by exclusively using prepared statements for SQL queries and effectively escaping most of its output. The lack of file operations, external HTTP requests, and dangerous functions further contributes to its robustness. However, a significant concern arises from the presence of one unprotected AJAX handler, which represents a direct entry point that could be exploited without proper authentication or authorization checks. This oversight, while not immediately catastrophic given the other positive indicators, introduces a vulnerability that needs urgent attention. The plugin's maturity and stability are further suggested by its lack of recorded vulnerabilities, implying a diligent development process. Overall, 'eloquent' v0.2 is a promising plugin with a solid foundation, but the single unprotected AJAX endpoint poses a clear and present risk that must be addressed to maintain its secure state.

Key Concerns

  • Unprotected AJAX handler found
Vulnerabilities
None known

Eloquent Security Vulnerabilities

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

Eloquent Code Analysis

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

Output Escaping

86% escaped14 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
saveSelectors (src\EloquentPlugin.php:155)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
1 unprotected

Eloquent Attack Surface

Entry Points4
Unprotected1

AJAX Handlers 4

authwp_ajax_create_autodetect_entrysrc\EloquentOptions.php:11
authwp_ajax_save_postsrc\EloquentPlugin.php:15
authwp_ajax_save_selectorssrc\EloquentPlugin.php:16
authwp_ajax_publish_postsrc\EloquentPlugin.php:17
WordPress Hooks 7
actionadmin_menusrc\EloquentOptions.php:7
actionadmin_initsrc\EloquentOptions.php:8
actionadmin_footersrc\EloquentOptions.php:9
actionadmin_enqueue_scriptssrc\EloquentOptions.php:10
actionadmin_noticessrc\EloquentOptions.php:17
actionafter_switch_themesrc\EloquentOptions.php:19
actionwp_enqueue_scriptssrc\EloquentPlugin.php:13
Maintenance & Trust

Eloquent Maintenance & Trust

Maintenance Signals

WordPress version tested5.9.13
Last updatedMay 19, 2022
PHP min version
Downloads1K

Community Trust

Rating100/100
Number of ratings3
Active installs10
Developer Profile

Eloquent Developer Profile

Avram

6 plugins · 410 total installs

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

How We Detect Eloquent

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/eloquent/swal/sweetalert.css/wp-content/plugins/eloquent/swal/sweetalert.min.js
Script Paths
/wp-content/plugins/eloquent/swal/sweetalert.min.js
Version Parameters
eloquent/swal/sweetalert.min.js?ver=

HTML / DOM Fingerprints

CSS Classes
eloquent-placeholder
Data Attributes
eloquentAutoDetect('post')eloquentAutoDetect('page')
JS Globals
eloquentAutoDetectSwal
REST Endpoints
/wp-json/wp/v2/posts
FAQ

Frequently Asked Questions about Eloquent