CVE-2025-53273
BaseFortify
Publication date: 2025-06-27
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 Slickstream plugin versions up to 2.0.3. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent. The attacker does not need to be authenticated themselves to exploit this issue. It falls under the OWASP Top 10 category A1: Broken Access Control and has a low severity rating. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unwanted actions on your site through authenticated users, potentially compromising the integrity of your site. Although the severity is low and the impact is limited, it could lead to unauthorized changes or disruptions if exploited. There is currently no official patch, 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 involves monitoring for suspicious actions executed by authenticated users that could be triggered by CSRF attacks. Since no specific detection commands are provided, it is recommended to perform server-side malware scanning and seek professional incident response if compromise is suspected. Plugin-based malware scanners may be unreliable for this vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) to auto-mitigate the vulnerability without official patches. Additionally, monitoring for suspicious activity and considering professional incident response or server-side malware scanning is advised. Since no official fix or patched version is available, virtual patching provides rapid protection without performance loss. [1]