CVE-2023-1923

WP Fastest Cache <= 1.1.2 - Cross-Site Request Forgery via 'wpfc_remove_cdn_integration_ajax_request_callback'

2023-04-06 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 1.1.3
Affected Plugin
WP Fastest Cache – WordPress Cache Plugin
Affected Version
<= 1.1.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-1923
View all WP Fastest Cache – WordPress Cache Plugin vulnerabilities

At a glance

CVE-2023-1923 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Fastest Cache WordPress plugin, affecting versions <= 1.1.2. 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 1.1.3; sites on affected versions should update now. Disclosed April 2023, reported by Marco Wotschka.

Vulnerability Overview

The WP Fastest Cache plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.2. This is due to missing or incorrect nonce validation on the wpfc_remove_cdn_integration_ajax_request_callback function. This makes it possible for unauthenticated attackers to change cdn 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)

Reaching this weakness in WP Fastest Cache <= 1.1.2 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 WP Fastest Cache the fix is 1.1.3: builds <= 1.1.2 are affected, anything from 1.1.3 onward is not.

Remediation

Update to version 1.1.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-1923https://www.wordfence.com/threat-intel/vulnerabilities/id/49ba5cfa-c2cc-49ac-b22d-7e36ccca6ac5https://nvd.nist.gov/vuln/detail/CVE-2023-1923

Related records

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