CVE-2025-53263
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 plugin "Address Autocomplete via Google for Gravity Forms" versions up to 1.3.4. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising site integrity. The vulnerability is related to broken access control and does not require authentication to exploit. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unwanted actions on your WordPress site when higher privileged users are tricked into performing these actions unknowingly. This can compromise the integrity of your site, potentially leading to unauthorized changes or disruptions. However, the risk is considered low severity with a CVSS score of 5.4, and it is unlikely to be widely exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific commands or detection methods provided for identifying this vulnerability on your network or system. Detection would typically involve monitoring for suspicious CSRF attack patterns or checking the plugin version to see if it is up to 1.3.4, which is vulnerable. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which provides automatic protection even without an official fix. Additionally, monitor for plugin updates and consider restricting access or disabling the vulnerable plugin until a patch is available. [1]