WP Fastest Cache <= 1.1.2 - Missing Authorization in 'wpfc_preload_single_callback'
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-862 · Missing Authorization
- CVE
CVE-2023-1928
At a glance
CVE-2023-1928 is a medium-severity Missing Authorization 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). The root cause is a missing authorization check on a reachable function. 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 unauthorized data modification due to a missing capability check on the wpfc_preload_single_callback function in versions up to, and including, 1.1.2. This makes it possible for authenticated attackers with subscriber-level access to initiate cache creation.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in WP Fastest Cache <= 1.1.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. 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.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Fastest Cache – WordPress Cache Plugin
- 9.8CVE-2023-6063: WP Fastest Cache <= 1.2.1 SQL Injection
CVE-2023-6063 - 9.8CVE-2015-9316: WP Fastest Cache < 0.8.4.9 SQL Injection
CVE-2015-9316 - 9.1CVE-2019-13635: WP Fastest Cache <= 0.8.9.5 Directory Traversal
CVE-2019-13635 - 8.8CVE-2021-24870: WP Fastest Cache CSRF to Stored Cross-Site Scripting
CVE-2021-24870 - 8.8CVE-2021-24869: WP Fastest Cache < 0.9.5 SQL Injection
CVE-2021-24869 - 8.8CVE-2018-17584: WP Fastest Cache <= 0.8.8.5 Cross-Site Request Forgery
CVE-2018-17584 - 8.8WP Fastest Cache <= 0.8.5.9 Local File Inclusion
- 8.8WP Fastest Cache <= 0.8.5.7 Local File Inclusion
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C