CVE-2025-53269
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) issue in the WordPress My Wp Brand plugin versions up to 1.1.3. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising the site's integrity. The vulnerability requires no privileges to initiate and is classified under OWASP Top 10 category A1: Broken Access Control. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unauthorized actions on your WordPress site through tricking privileged users. This can lead to compromised site integrity, unauthorized changes, or other malicious activities performed under the guise of a legitimate user. Although it has a low severity rating and is considered low priority, it still poses a risk to site security. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or network indicators provided for this vulnerability. Users are advised to monitor for suspicious activity involving unauthorized actions executed by authenticated users, but no explicit detection commands are mentioned. [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 performance loss. Since no official patch is available, users should monitor for updates, consider restricting user privileges, and engage professional incident response if compromise is suspected. [1]