CVE-2023-41801

AWP Classifieds <= 4.3 - Cross-Site Request Forgery

2023-09-05 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 4.3.1
Affected Plugin
AWP Classifieds
Affected Version
<= 4.3
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-41801
View all AWP Classifieds vulnerabilities

At a glance

CVE-2023-41801 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the AWP Classifieds WordPress plugin, affecting versions <= 4.3. 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 4.3.1; sites on affected versions should update now. Disclosed September 2023, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The AWP Classifieds plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.3. This is due to missing nonce validation on several functions such as dispatch(), try_to_delete_categories(), try_to_update_category(), try_to_move_categories(), and more. This makes it possible for unauthenticated attackers to manage categories 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)

AWP Classifieds <= 4.3 carries this weakness at dispatch(), 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 AWP Classifieds the fix is 4.3.1: builds <= 4.3 are affected, anything from 4.3.1 onward is not.

Remediation

Update to version 4.3.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-41801https://www.wordfence.com/threat-intel/vulnerabilities/id/b06a1b66-9057-4f16-878c-4fa66489f0ffhttps://nvd.nist.gov/vuln/detail/CVE-2023-41801

Related records

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