WordPress plugin
WPGlobus Translate Options security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium2
- Low0
All WPGlobus Translate Options vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Stored Cross-Site Scripting ≤2.2.0No patch available | CVE-2024-9434 | |
| Medium6.1 | Reflected Cross-Site Scripting via page ≤2.1.0Update to 2.2.0 | CVE-2023-25711 |
- Medium6.1Cross-Site Request Forgery to Stored Cross-Site Scripting
≤2.2.0No patch available
- Medium6.1Reflected Cross-Site Scripting via page
≤2.1.0Update to 2.2.0
WPGlobus Translate Options: common questions
Does WPGlobus Translate Options have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in WPGlobus Translate Options: 2 medium. At least one is not fixed in the latest version.
How do I check which version of WPGlobus Translate Options I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent WPGlobus Translate Options vulnerability?
CVE-2024-9434, published Oct 30, 2024: WPGlobus Translate Options <= 2.2.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any WPGlobus Translate Options vulnerability listed in CISA KEV?
No. None of the known WPGlobus Translate Options vulnerabilities is currently listed in the CISA KEV catalog.