LiveActive security incident?Get immediate response
CVE Record

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

A vulnerability was found in Kau-Boy Backend Localization Plugin up to 1.6.1 on WordPress. It has been rated as problematic. This issue affects some unknown processing of the file backend_localization.php. The manipulation leads to cross site scripting. The attack may be initiated remotely. Upgrading to version 2.0 is able to address this issue. The patch is named 43dc96defd7944da12ff116476a6890acd7dd24b. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-227231.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a cross-site scripting flaw in the Kau-Boy Backend Localization Plugin for WordPress. An authenticated remote user could manipulate affected plugin processing and cause unintended script execution. The known fix is upgrading to version 2.0. Evidence supplied does not show active exploitation.

Executive priority

Prioritize remediation during the next WordPress maintenance window, sooner for externally managed or multi-user sites. The issue is not marked as actively exploited, but XSS in a WordPress plugin can still create operational and trust risk.

Technical view

CVE-2012-10013 affects backend_localization.php in Kau-Boy Backend Localization Plugin up to 1.6.1. It is classified as CWE-79 with CVSS 2.0 score 4.0: network reachable, low complexity, authentication required, partial integrity impact, no confidentiality or availability impact. Version 2.0 and commit 43dc96defd7944da12ff116476a6890acd7dd24b address it.

Likely exposure

Exposure is likely limited to WordPress sites running Kau-Boy Backend Localization Plugin versions 1.6.0 or 1.6.1, or otherwise up to 1.6.1. The CVSS vector indicates authentication is required, reducing internet-wide risk compared with unauthenticated XSS.

Exploitation context

The source bundle says the attack may be initiated remotely and requires authentication. It does not include KEV listing, active exploitation evidence, public exploit details, or confirmed attacker activity. Treat this as a patchable medium-risk plugin issue unless local exposure suggests higher business impact.

Researcher notes

Key unknowns remain: the exact vulnerable parameter or workflow is not described in the provided summary, and CPE data is absent. Validation should focus on confirmed plugin presence, version, authentication boundaries, and whether the 2.0 patch is deployed.

Mitigation direction

  • Inventory WordPress sites for Kau-Boy Backend Localization Plugin versions up to 1.6.1.
  • Upgrade the affected plugin to version 2.0.
  • Confirm the deployed code includes patch commit 43dc96defd7944da12ff116476a6890acd7dd24b.
  • If upgrade is delayed, restrict access to trusted authenticated users.
  • Consult vendor or repository guidance before choosing temporary alternatives.

Validation and detection

  • Check WordPress plugin inventory for the affected plugin and version.
  • Verify version 2.0 is installed after remediation.
  • Compare deployed plugin code against the referenced patch when version data is unreliable.
  • Review recent authenticated user activity for unexpected plugin or content changes.
Prepared
Confidence
high
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-10013 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-10013Access 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 Plugin1.6.0, 1.6.1Listed
Weakness

CWE details

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