EVE Dynamic Prerender Security & Risk Analysis

wordpress.org/plugins/eve-dynamic-prerender

An easy and powerful plugin to implement a real dynamic Prerender Meta Tag inside the head section of the HTML document. This version use AJAX so it w …

10 active installs v4.0.1 PHP + WP 2.5+ Updated May 16, 2019
loading-speedpage-load-timeperformanceprerenderseo
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is EVE Dynamic Prerender Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The eve-dynamic-prerender plugin exhibits a concerning security posture primarily due to its unprotected entry points. The static analysis reveals two AJAX handlers that lack any authentication or capability checks, presenting a significant attack surface. Furthermore, all identified output operations are unescaped, meaning user-controlled data displayed on the frontend could be vulnerable to cross-site scripting (XSS) attacks. The taint analysis confirms two flows with unsanitized paths, highlighting potential risks where data might not be properly validated or cleaned before use.

Despite these critical flaws, the plugin does not have a known vulnerability history, with zero recorded CVEs. This could indicate either a lack of past security issues or a lack of rigorous historical security auditing. The presence of prepared statements for most SQL queries is a positive sign, demonstrating good database interaction practices. However, the absence of nonce checks and capability checks in conjunction with the unprotected AJAX endpoints creates a scenario where an attacker could potentially trigger unintended actions or access sensitive data without proper authorization.

In conclusion, while the plugin shows some good practices like using prepared statements, the critical deficiencies in input validation and output escaping, coupled with unprotected AJAX handlers, pose significant risks. The absence of historical vulnerabilities is a positive but not a definitive indicator of current security. Remediation of the unescaped outputs and the unprotected AJAX handlers is paramount to improving its security.

Key Concerns

  • Unprotected AJAX handlers
  • Unescaped output
  • Taint flow with unsanitized path (critical)
  • Taint flow with unsanitized path (critical)
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

EVE Dynamic Prerender Security Vulnerabilities

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

EVE Dynamic Prerender Code Analysis

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

SQL Query Safety

88% prepared8 total queries

Output Escaping

0% escaped3 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
eve_prerender (eve_prerender.php:129)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

EVE Dynamic Prerender Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_eve_ajax_prerendereve_prerender.php:29
noprivwp_ajax_eve_ajax_prerendereve_prerender.php:30
WordPress Hooks 2
actionwp_headeve_prerender.php:27
actionwp_footereve_prerender.php:28
Maintenance & Trust

EVE Dynamic Prerender Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedMay 16, 2019
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

EVE Dynamic Prerender Developer Profile

gsacheli

1 plugin · 10 total installs

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

How We Detect EVE Dynamic Prerender

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

Asset Fingerprints

Script Paths
/wp-content/plugins/eve-dynamic-prerender/eve_prerender.php

HTML / DOM Fingerprints

HTML Comments
<!-- Plugin Name: EVE Dynamic Prerender Meta Tag Plugin URI: https://www.evemilano.com/2017/11/wp-prerender-plugin/ Version: 4.0.1 Description: Prerender Meta Tag allows webmaster to pre-load in background a second page in the browser. This plugin uses the navigation data to guess the next page that the user will visit. Let the plugin work for some day to improve the prerender. From version 4.0 it uses AJAX and it works also with caching systems. Author: Giovanni Sacheli Author URI: https://www.evemilano.com/ --><!-- Modifiche effettuate: Innanzitutto ho pulito un po' il codice e sistemato in alcuni punti come vengono eseguite le query utilizzando placeholder e quant'altro; Ho fixato il fatto che se non vi è settato il permalink da inserire nel prerender e sono in homepage, non stampo il tag meta prerender; Passaggio ad AJAX Innanzitutto ho rimosso dalla funzione eve_prerender il salvataggio del match (sennò sarebbe duplicato insieme a quello via AJAX); la stampa dei tag l'ho comunque lasciato per tenerlo impresso nella cache La funzione eve_render_javascript stampa nel footer la funzione JS in AJAX che richede (con parametri il referrer e l'attuale link), l'eventuale tag prerender e referrer; Nella funzione eve_ajax_prerender (la funziona attivata dall'AJAX), sono stati inseriti i passaggi SQL per il match dei due link per creare il prerender, e per restituire alla chiamata poi il match eventuale con referrer e prerender; -->
Data Attributes
rel='prerender'name='referrer'
JS Globals
window.locationdocument.referreradmin_url('admin-ajax.php')json_encodejQuery$
REST Endpoints
/wp-json/
FAQ

Frequently Asked Questions about EVE Dynamic Prerender