dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-11034

HIGH · 7.3 CVSS v3.1 Published 2024-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The The Request a Quote for WooCommerce and Elementor – Get a Quote Button – Product Enquiry Form Popup – Product Quotation plugin for WordPress is vulnerable to arbitrary shortcode execution via fire_contact_form AJAX action in all versions up to, and including, 1.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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 confidence

The plugin's AJAX action 'fire_contact_form' accepts user input and passes it directly to do_shortcode() without validating the input or checking user permissions. This allows unauthenticated attackers to execute any registered WordPress shortcode by supplying arbitrary shortcode names as the input parameter.

MitigationImmediately restrict the AJAX action to authenticated users only and add proper input validation/allowlisting before executing do_shortcode. Until a patched version is released, consider disabling the plugin or blocking the fire_contact_form AJAX endpoint at the server level.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin containing the vulnerable AJAX action
    Search your WordPress plugins directory (wp-content/plugins) for files containing the string 'fire_contact_form' or check your site's AJAX handlers at /wp-admin/admin-ajax.php?action=fire_contact_form
    Affected if The plugin with the 'fire_contact_form' AJAX action is installed and active on the site
  2. Verify the AJAX endpoint is exposed to unauthenticated users
    Check the plugin's PHP code for wp_ajax_nopriv_fire_contact_form or wp_ajax_fire_contact_form hooks, or test accessing the AJAX endpoint without authentication: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=fire_contact_form'
    Affected if The endpoint responds without requiring login credentials (wp_ajax_nopriv_ is registered)
  3. Confirm the vulnerable do_shortcode call exists
    Examine the PHP handler function for fire_contact_form in the plugin source code and look for direct passing of user input to do_shortcode() without sanitization or permission checks
    Affected if The code passes $_POST or $_REQUEST parameters directly to do_shortcode() without validation
  4. Test shortcode execution capability
    Send a request with a known shortcode name as the action parameter, for example: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=fire_contact_form&shortcode=[any_valid_shortcode]'
    Affected if The response contains output from the shortcode, indicating arbitrary shortcode execution is possible

Your environment is affected if a plugin with the 'fire_contact_form' AJAX action is active, the endpoint is accessible to unauthenticated users, and the code passes unsanitized input directly to do_shortcode().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict the AJAX action to authenticated users only and add proper input validation/allowlisting before executing do_shortcode. Until a patched version is released, consider disabling the plugin or blocking the fire_contact_form AJAX endpoint at the server level.

Recommended fix Moderate confidence

Version higher than 1.4 (check WordPress plugin repository for current stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Request a Quote for WooCommerce and Elementor' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version which contains the security fix

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11034 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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