LiveActive security incident?Get immediate response
CVE Record

CVE-2012-10014: Kau-Boy Backend Localization Plugin backend_localization.php localize_backend cross site scripting

A vulnerability classified as problematic has been found in Kau-Boy Backend Localization Plugin 2.0 on WordPress. Affected is the function backend_localization_admin_settings/backend_localization_save_setting/backend_localization_login_form/localize_backend of the file backend_localization.php. The manipulation leads to cross site scripting. It is possible to launch the attack remotely. Upgrading to version 2.0.1 is able to address this issue. The name of the patch is 36f457ee16dd114e510fd91a3ea9fbb3c1f87184. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-227232.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using Kau-Boy Backend Localization Plugin 2.0. A remote authenticated user could trigger cross-site scripting in backend localization code, potentially running script in another user's browser and affecting administrative workflows. It is not listed as known exploited in KEV, and the provided sources identify version 2.0.1 as the fix.

Executive priority

Treat as a moderate-priority cleanup item. It is not supported by supplied evidence as actively exploited, but affected WordPress admin surfaces should be upgraded promptly, especially where many users have backend access.

Technical view

CVE-2012-10014 is a CWE-79 XSS issue in backend_localization.php, involving backend_localization_admin_settings, backend_localization_save_setting, backend_localization_login_form, and localize_backend. The supplied CVSS v2 vector is AV:N/AC:L/Au:S/C:N/I:P/A:N, score 4.0, indicating network reachability, low complexity, authentication required, and partial integrity impact.

Likely exposure

Exposure is limited to WordPress installations running Kau-Boy Backend Localization Plugin version 2.0. The CVSS vector indicates the attacker must be authenticated, reducing broad internet risk but leaving multi-user or delegated-admin WordPress environments exposed.

Exploitation context

The source bundle says remote exploitation is possible, but authentication is required. No CISA KEV listing or supplied reference indicates active exploitation. The available evidence does not establish public weaponization or exploitation in the wild.

Researcher notes

The provided sources identify affected functions and file but do not include detailed exploit prerequisites beyond authenticated remote XSS. Avoid assuming unauthenticated impact. Validation should focus on version, patch presence, and WordPress role exposure.

Mitigation direction

  • Upgrade Kau-Boy Backend Localization Plugin from 2.0 to 2.0.1.
  • Confirm the patch commit 36f457ee16dd114e510fd91a3ea9fbb3c1f87184 is present.
  • Restrict WordPress administrative access to trusted users only.
  • Review vendor or plugin repository guidance for any additional hardening steps.

Validation and detection

  • Inventory WordPress sites for Kau-Boy Backend Localization Plugin installations.
  • Verify installed plugin version is not 2.0.
  • Check plugin code provenance against the 2.0.1 release or patch commit.
  • Review admin-user activity for unusual localization setting changes.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-10014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 2.0MediumAV:N/AC:L/Au:S/C:N/I:P/A:N82.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

4Medium
CVSS 2.0 vector shape for CVE-2012-10014Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Kau-BoyBackend Localization Plugin2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.