Request a Quote <= 2.3.10 - Cross-Site Request Forgery

2023-06-30 00:00
Anonymous

Strategic Overview

Status
Patched in 2.3.11
Affected Plugin
Request a Quote – Quote Forms for Any WordPress Site
Affected Version
< 2.3.11
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Request a Quote – Quote Forms for Any WordPress Site vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Request a Quote WordPress plugin, affecting versions < 2.3.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.3.11; sites on affected versions should update now. Disclosed June 2023.

Vulnerability Overview

The Request a Quote plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.10. This is due to missing nonce validation on the emd_show_forms_lite_page() function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Request a Quote < 2.3.11 carries this weakness at emd_show_forms_lite_page(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Request a Quote the fix is 2.3.11: builds < 2.3.11 are affected, anything from 2.3.11 onward is not.

Remediation

Update to version 2.3.11, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Request a Quote: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Request a Quote 2.3.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/9854d09a-2fab-46e6-9fc1-ff6d68df2662

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C