CVE-2025-7669
BaseFortify
Publication date: 2025-07-19
Last updated on: 2025-07-22
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| avishika | avishi_wp_paypal_payment_button | * |
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) issue in the Avishi WP PayPal Payment Button WordPress plugin versions up to 2.0. It occurs because the plugin's 'avishi-wp-paypal-payment-button/index.php' page lacks proper nonce validation, allowing attackers to trick a site administrator into performing unintended actions, such as updating settings or injecting malicious scripts, by sending forged requests.
How can this vulnerability impact me? :
The vulnerability can allow unauthenticated attackers to manipulate the plugin's settings or inject malicious web scripts if they can trick a site administrator into clicking a malicious link. This can lead to compromised site integrity, potential unauthorized changes, and possible injection of harmful code affecting site visitors.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately disable or uninstall the Avishi WP PayPal Payment Button plugin if it is installed on your WordPress site, as the plugin has been temporarily closed and is unavailable for download pending a full review. Additionally, avoid clicking on suspicious links that could trigger forged requests, and ensure that site administrators are aware of the risk of Cross-Site Request Forgery attacks related to this plugin. Monitor for plugin updates or patches from the developers before re-enabling it. [1]