Answer in brief
CVE-2026-14249 records a High severity (CVSS 7.5) vulnerability in Request a Quote Form Plugin <= 2.5.5 - Unauthenticated Code Injection via 'path' Parameter. The current sources do not mark it as known exploited. The current feed maps emarket-design/Request a Quote – Quote Forms for Any WordPress Site (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-14249 records a High severity (CVSS 7.5) vulnerability in Request a Quote Form Plugin <= 2.5.5 - Unauthenticated Code Injection via 'path' Parameter. The current sources do not mark it as known exploited. The current feed maps emarket-design/Request a Quote – Quote Forms for Any WordPress Site (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps emarket-design/Request a Quote – Quote Forms for Any WordPress Site (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| emarket-design/Request a Quote – Quote Forms for Any WordPress Sitegeneric | 0 | Not reported |
Published upstream
Jul 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
The Request a Quote plugin for WordPress is vulnerable to Code Injection in versions up to, and including, 2.5.5 via the emd_delete_file AJAX action. This is due to the emd_delete_file() handler deriving a PHP function name from the attacker-controlled $_POST['path'] parameter and invoking it dynamically via the variable-function call $sess_name(), and the handler being registered for wp_ajax_nopriv with its only protection being a nonce that the plugin prints into the public quote-form page via wp_localize_script. This makes it possible for unauthenticated attackers to invoke arbitrary zero-argument PHP functions on the server, such as phpinfo(), potentially exposing sensitive server configuration and credentials, or executing other destructive built-in PHP functions.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps emarket-design/Request a Quote – Quote Forms for Any WordPress Site (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| emarket-design/Request a Quote – Quote Forms for Any WordPress Sitegeneric | 0 | Not reported |
Published upstream
Jul 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
The Request a Quote plugin for WordPress is vulnerable to Code Injection in versions up to, and including, 2.5.5 via the emd_delete_file AJAX action. This is due to the emd_delete_file() handler deriving a PHP function name from the attacker-controlled $_POST['path'] parameter and invoking it dynamically via the variable-function call $sess_name(), and the handler being registered for wp_ajax_nopriv with its only protection being a nonce that the plugin prints into the public quote-form page via wp_localize_script. This makes it possible for unauthenticated attackers to invoke arbitrary zero-argument PHP functions on the server, such as phpinfo(), potentially exposing sensitive server configuration and credentials, or executing other destructive built-in PHP functions.
Quoted source text, attributed separately from HOL analysis.