CVE-2022-47447

WP-Advanced-Search <= 3.3.8 - Cross-Site Request Forgery leading to Plugin Settings Updates

2023-03-14 00:00
rezaduty

Strategic Overview

Status
Patched in 3.3.9
Affected Plugin
WordPress WP-Advanced-Search
Affected Version
<= 3.3.8
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-47447
View all WordPress WP-Advanced-Search vulnerabilities

At a glance

CVE-2022-47447 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WordPress WP-Advanced-Search WordPress plugin, affecting versions <= 3.3.8. 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 3.3.9; sites on affected versions should update now. Disclosed March 2023, reported by rezaduty.

Vulnerability Overview

The WP-Advanced-Search plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.3.8. This is due to missing or incorrect nonce validation on the 'WP_Advanced_Search_update_pagination', 'WP_Advanced_Search_update_styles', 'WP_Advanced_Search_Autocomplete_Action, and possibly other functions. This makes it possible for unauthenticated attackers to update certain plugin 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)

WordPress WP-Advanced-Search <= 3.3.8 carries this weakness at WP_Advanced_Search_update_pagination, 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 WordPress WP-Advanced-Search the fix is 3.3.9: builds <= 3.3.8 are affected, anything from 3.3.9 onward is not.

Remediation

Update to version 3.3.9, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-47447https://www.wordfence.com/threat-intel/vulnerabilities/id/a2ba21cd-d8f3-402a-b067-1758937d9eb4https://nvd.nist.gov/vuln/detail/CVE-2022-47447

Related records

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