CVE-2025-49317
BaseFortify
Publication date: 2025-06-06
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) in the WordPress WP Page Loading plugin versions up to 1.0.6. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising site integrity. The vulnerability requires no authentication to exploit and is classified under OWASP Top 10 A1: Broken Access Control. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unwanted actions on your WordPress site through the WP Page Loading plugin if you have a higher privileged user authenticated. This can lead to compromised site integrity, unauthorized changes, or other malicious activities. However, the severity is considered low with a CVSS score of 4.3, and the likelihood of exploitation is low. Updating to version 1.0.7 or later is recommended to mitigate this risk. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if the WordPress WP Page Loading plugin version 1.0.6 or earlier is installed on your system. You can check the plugin version via the WordPress admin dashboard or by inspecting the plugin files. There are no specific network commands provided for detection. A practical approach is to verify the plugin version and update if vulnerable. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the WP Page Loading plugin to version 1.0.7 or later, where the issue is fixed. Alternatively, you can apply virtual patching (vPatching) offered by Patchstack to protect your site automatically before applying the official patch. Additionally, ensure timely updates and monitor for any suspicious activity as part of professional incident response. [1]