CVE-2025-30946
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 Custom Bulk/Quick Edit plugin versions up to 1.6.10. It allows an attacker to trick authenticated users with higher privileges into executing unwanted actions on the site without their consent, potentially compromising site integrity. Exploitation does not require authentication, but the impact is considered low. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized actions being performed on your WordPress site by tricking privileged users into executing them. This may compromise the integrity of your site, although the severity is low and exploitation is unlikely to be widespread. There is no official patch yet, but virtual patching is available as a mitigation. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability is challenging as plugin-based malware scanners may be unreliable. There are no specific commands provided to detect the vulnerability on your network or system. Users are advised to seek professional incident response or hosting provider assistance for detection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which auto-mitigates the vulnerability without an official fix. Additionally, users should consider disabling or removing the vulnerable plugin version (up to 1.6.10) until a fix is available, and seek professional incident response or hosting provider assistance if compromise is suspected. [1]