WordPress plugin
Backend Localization 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
- Medium3
- Low0
All Backend Localization vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery ≤2.1.10No patch available | CVE-2023-44471 | |
| Medium6.1 | Reflected Cross-Site Scripting ≤2.0Update to 2.0.1 | CVE-2012-10014 | |
| Medium6.1 | Reflected Cross-Site Scripting 1.6.1 – 1.6.1Update to 2.0 | CVE-2012-10013 |
- Medium4.3Cross-Site Request Forgery
≤2.1.10No patch available
- Medium6.1Reflected Cross-Site Scripting
≤2.0Update to 2.0.1
- Medium6.1Reflected Cross-Site Scripting
1.6.1 – 1.6.1Update to 2.0
Backend Localization: common questions
Does Backend Localization have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Backend Localization: 3 medium. At least one is not fixed in the latest version.
How do I check which version of Backend Localization 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 Backend Localization vulnerability?
CVE-2023-44471, published Sep 29, 2023: Backend Localization <= 2.1.10 - Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any Backend Localization vulnerability listed in CISA KEV?
No. None of the known Backend Localization vulnerabilities is currently listed in the CISA KEV catalog.