CVE-2025-48111
BaseFortify
Publication date: 2025-06-17
Last updated on: 2025-06-17
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 YITH PayPal Express Checkout for WooCommerce plugin (versions up to 1.49.0). It allows a malicious actor to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising the site's integrity. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized actions being executed on your WooCommerce site by tricking privileged users. This can compromise the integrity of your site, potentially leading to unwanted changes or disruptions in the PayPal Express Checkout process. Although the severity is low, it still poses a risk to site security and user trust. [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 installed version of the YITH PayPal Express Checkout for WooCommerce plugin is version 1.49.0 or earlier, as these versions are vulnerable. There are no specific network commands provided to detect exploitation attempts. Checking the plugin version via the WordPress admin dashboard or using WP-CLI commands such as 'wp plugin list' to verify the installed version can help detect vulnerability presence. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the YITH PayPal Express Checkout for WooCommerce plugin to version 1.49.1 or later, where the vulnerability is fixed. Alternatively, applying virtual patching (vPatching) provided by Patchstack can serve as an immediate mitigation by auto-applying security rules before official patches are released. If a compromise is suspected, seeking professional incident response is recommended. [1]