CVE-2023-48323

Awesome Support <= 6.1.4 - Cross-Site Request Forgery via wpas_edit_reply_ajax()

2023-11-23 00:00
thiennv

Strategic Overview

Status
Patched in 6.1.5
Affected Plugin
Awesome Support – WordPress HelpDesk & Support Plugin
Affected Version
<= 6.1.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-48323
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2023-48323 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.1.4. 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 6.1.5; sites on affected versions should update now. Disclosed November 2023, reported by thiennv.

Vulnerability Overview

The Awesome Support plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.1.4. This is due to missing or incorrect nonce validation on the wpas_edit_reply_ajax() function. This makes it possible for unauthenticated attackers to edit replies 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)

Awesome Support <= 6.1.4 carries this weakness at wpas_edit_reply_ajax(), 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 Awesome Support the fix is 6.1.5: builds <= 6.1.4 are affected, anything from 6.1.5 onward is not.

Remediation

Update to version 6.1.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-48323https://www.wordfence.com/threat-intel/vulnerabilities/id/579b887a-4140-4e12-9a9a-ba52d212b8a2https://nvd.nist.gov/vuln/detail/CVE-2023-48323

Related records

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