CVE-2026-14249
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Request a Quote WordPress plugin (versions up to 2.5.5) contains a code injection vulnerability in the emd_delete_file AJAX action. The handler derives a PHP function name from the attacker-controlled $_POST['path'] parameter and executes it via dynamic variable-function call ($sess_name()). Since the action is registered with wp_ajax_nopriv, it is accessible to unauthenticated users, and the nonce protection printed via wp_localize_script can be bypassed, allowing execution of arbitrary zero-argument PHP functions like phpinfo().
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionCheck the WordPress plugin directory for 'request-a-quote' or 'emd' plugin folder, and read the main plugin file header for the Version fieldAffected if The version number is 2.5.5 or lower, or no version is listed (implying an unpatched version)
-
Confirm the emd_delete_file AJAX action existsCheck the plugin's main PHP file for the string 'emd_delete_file' and verify it is registered as an AJAX action hookAffected if The emd_delete_file action hook is present in the plugin code
-
Verify the AJAX endpoint is accessible to unauthenticated usersSearch the plugin code for 'wp_ajax_nopriv_amd_delete_file' or a call to add_action('wp_ajax_nopriv_emd_delete_file', ...)Affected if The action is registered with wp_ajax_nopriv, making it accessible without authentication
-
Inspect the vulnerable function handlerLocate the emd_delete_file callback function and examine how the $_POST['path'] parameter is processed - look for dynamic function calls using variable variables like $$sess_name or similar patternsAffected if The code uses the $_POST['path'] parameter to construct or call a PHP function dynamically without proper validation
-
Test endpoint accessibility externally (optional)If accessible, send a POST request to /wp-admin/admin-ajax.php with action=emd_delete_file and a test path parameter to confirm the endpoint respondsAffected if The AJAX endpoint responds without requiring authentication
The environment is affected if the Request a Quote plugin version is 2.5.5 or lower AND the emd_delete_file AJAX action exists and is registered for unauthenticated access with dynamic function execution logic present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched version of the plugin that properly validates the path parameter against an allowlist and enforces proper capability checks or nonce verification. Until a patch is available, consider disabling the plugin or blocking the emd_delete_file AJAX endpoint at the web server level.
Request a Quote plugin version 2.5.6 or later
- Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
- Locate the 'Request a Quote' plugin in the plugin list
- Check the current installed version - if it is 2.5.5 or earlier, an update is available
- Click 'Update Now' to install the latest version, which should be 2.5.6 or higher
- After updating, verify the plugin is active and the quote functionality works correctly
- Confirm the emd_delete_file AJAX action is no longer vulnerable to arbitrary function invocation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14249 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data