Plugins · request-a-quote · data as of 2026-11-04
Is Request a Quote safe? Known vulnerabilities and latest version
- Status
- Closed 2026-09-21
- Known issues on record
- 9
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate request-a-quote && wp plugin delete request-a-quote
Check your version
Known vulnerabilities
9 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 9 record(s) do not state which versions are affected.
medium 5.3 CVE-2026-90988 · published 2026-10-02
Information disclosure in Request a Quote (2.5.6 and older)
- Affected
- 2.5.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Request a Quote WordPress plugin through 2.5.6 does not perform an authorization check on one of its unauthenticated AJAX handlers, allowing unauthenticated users to read the contact records of quote-request submissions, including records the site has not published.
high 7.5 CVE-2026-14249 · published 2026-07-02
Remote code execution in Request a Quote (2.5.5 and older)
- Affected
- 2.5.5 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-14249Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2025-64248 · published 2025-12-16
Missing authorization check in Request a Quote (2.5.3 and older)
- Affected
- 2.5.3 and older
- Fixed in
- 2.5.4
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in emarket-design Request a Quote request-a-quote allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Request a Quote: from n/a through <= 2.5.3.
medium 6.5 CVE-2025-58915 · published 2025-09-23
Stored cross-site scripting (XSS) in Request a Quote (2.5.0 and older)
- Affected
- 2.5.0 and older
- Fixed in
- 2.5.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in emarket-design Request a Quote request-a-quote allows Stored XSS.This issue affects Request a Quote: from n/a through <= 2.5.0.
medium 5.9 CVE-2024-6231 · published 2024-07-23
Stored cross-site scripting (XSS) in Request a Quote (older than 2.4.1)
- Affected
- older than 2.4.1
- Fixed in
- 2.4.1
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Request a Quote WordPress plugin before 2.4.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
medium 4.8 CVE-2022-2239 · published 2022-07-25
Cross-site scripting (XSS) in Request a Quote (older than 2.3.9)
- Affected
- older than 2.3.9
- Fixed in
- 2.3.9
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Request a Quote WordPress plugin before 2.3.9 does not sanitise and escape some of its settings, allowing high privilege users such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.
high 8.8 CVE-2022-2240 · published 2022-07-25
CSV injection in Request a Quote (2.3.7 to 2.3.7)
- Affected
- 2.3.7 to 2.3.7
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Request a Quote WordPress plugin through 2.3.7 does not validate uploaded CSV files, allowing unauthenticated users to attach a malicious CSV file to a quote, which could lead to a CSV injection once an admin download and open it
medium 4.8 CVE-2021-24489 · published 2021-10-25
Stored cross-site scripting (XSS) in Request a Quote (older than 2.3.9)
- Affected
- older than 2.3.9
- Fixed in
- 2.3.9
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Request a Quote WordPress plugin before 2.3.9 does not sanitise, validate or escape some of its settings in the admin dashboard, leading to authenticated Stored Cross-Site Scripting issues even when the unfiltered_html capability is disallowed.
medium 5.4 CVE-2021-24420 · published 2021-07-12
Stored cross-site scripting (XSS) in Request a Quote (older than 2.3.4)
- Affected
- older than 2.3.4
- Fixed in
- 2.3.4
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The Request a Quote WordPress plugin before 2.3.4 did not sanitise and escape some of its quote fields when adding/editing a quote as admin, leading to Stored Cross-Site scripting issues when the quote is output in the 'All Quotes" table.
Recent activity
- 2026-09-21 — closed on wordpress.org.
- 2026-10-02 — Information disclosure disclosed (CVE-2026-90988), fix version not stated.
- 2026-07-02 — Remote code execution disclosed (CVE-2026-14249), fix version not stated.
- 2025-12-16 — Missing authorization check disclosed (CVE-2025-64248), fixed in 2.5.4.
Get an email when Request a Quote has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Request a Quote (request-a-quote) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (5) · Sensitive data exposure (1) · Remote code execution (1) · Missing authorization (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/request-a-quote (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/request-a-quote"><img src="https://laskyr.com/plugins/request-a-quote/badge.svg" alt="Request a Quote vulnerability status"></a>