WP Fastest Cache Premium <= 1.7.4 - Missing Authorization to Authenticated (Subscriber+) Blind Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 1.7.5
- Affected Plugin
- WP Fastest Cache Premium
- Affected Version
<= 1.7.4- CVSS
- 3.5Low
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-10583
At a glance
CVE-2025-10583 is a low-severity Missing Authorization vulnerability in the WP Fastest Cache Premium WordPress plugin, affecting versions <= 1.7.4. It carries a CVSS score of 3.5 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.7.5; sites on affected versions should update now. Disclosed December 2025, reported by Dmitrii Ignatyev.
Vulnerability Overview
The WP Fastest Cache Premium plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.7.4 via the 'get_server_time_ajax_request' AJAX action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The free version is not affected.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Fastest Cache Premium <= 1.7.4 carries this weakness at get_server_time_ajax_request, and reaching it takes an account at Subscriber level or above. 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 Premium the fix is 1.7.5: builds <= 1.7.4 are affected, anything from 1.7.5 onward is not.
Remediation
Update to version 1.7.5, 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 Premium 1.7.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C