CVE-2025-30632
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-06-06

Last updated on: 2026-04-23

Assigner: Patchstack

Description
Cross-Site Request Forgery (CSRF) vulnerability in pozzad Global Translator global-translator allows Cross Site Request Forgery.This issue affects Global Translator: from n/a through <= 2.0.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-06
Last Modified
2026-04-23
Generated
2026-05-07
AI Q&A
2025-06-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Global Translator plugin (versions up to 2.0.2). 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. [1]


How can this vulnerability impact me? :

The impact of this vulnerability includes potential compromise of site integrity by allowing attackers to execute unauthorized actions through tricking privileged users. Although the severity is considered low (CVSS score 5.4), it can lead to broken access control and unauthorized changes on the site. Exploitation does not require authentication, but the likelihood is low. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

There are no specific detection commands provided for this vulnerability. However, monitoring for unusual or unauthorized actions performed by higher privileged users in the Global Translator plugin may help identify exploitation attempts. Using Patchstack's virtual patching can also help block exploitation attempts automatically. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying Patchstack's virtual patching (vPatching) to automatically block exploitation attempts since no official patch is available. Additionally, monitor for updates from the plugin developer and consider professional incident response if compromise is suspected. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart