CVE-2012-10014 LOW

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

Vendor Kau-Boy
Product Backend Localization Plugin
Weakness CWE-79 · XSS
Published April 24, 2023
Last update August 6, 2024

CVSS base score

3.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Backend Localization Plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in versions 2.0 and earlier. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users. The vulnerability requires user interaction to trigger. Site administrators should update to a version newer than 2.0.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers when they view affected pages.

Potential impact on your site

04Site Impact

Authenticated users can deface content or steal session tokens from administrators and other users.

Conditions required to exploit

05Prerequisites

Attacker must be logged in with low-level user privileges; victim must visit a page containing the injected script.

Key dates

06Disclosure timeline

April 24, 2023 CVE published
August 6, 2024 Record updated

Related vulnerabilities

08Related CVE