CVE-2025-48306
BaseFortify
Publication date: 2025-08-28
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| savyour | savyour_affiliate_partner | * |
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?
CVE-2025-48306 is a Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Savyour Affiliate Partner plugin (versions up to 2.1.4) that can lead to Stored Cross-Site Scripting (XSS). This means an attacker can trick authenticated users with higher privileges into performing unauthorized actions, which can result in malicious scripts being stored and executed on the site, potentially compromising it. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute unauthorized actions on your site by exploiting authenticated users, leading to stored malicious scripts (Stored XSS). This can compromise the security of your website, potentially allowing attackers to steal data, hijack user sessions, or perform other malicious activities. Since the plugin is abandoned and unpatched, the risk remains unless mitigated by virtual patches or removal. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include removing and replacing the Savyour Affiliate Partner plugin with an alternative plugin, as no official patch or fixed version is available. Applying a virtual patch (vPatch) provided by Patchstack can offer automatic protection against this vulnerability. Additionally, if your website has been compromised, seek professional incident response services. Simply deactivating the plugin does not eliminate the risk. [1]