CVE-2026-3332 MEDIUM

CVE-2026-3332: Xhanch - My Advanced Settings <= 1.1.2 - Cross-Site Request Forgery to Settings Update

Vendor Xhanch_Studio
Product Xhanch – My Advanced Settings
Weakness CWE-352 · CSRF
Published March 21, 2026
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Xhanch - My Advanced Settings plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.2. This is due to missing nonce validation in the `xms_setting()` function on the settings update handler. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Settings that can be modified include favicon URL, Google Analytics account ID, and various WordPress behavior toggles. The `favicon_url` and `ga_acc_id` values are output on the front-end without escaping, enabling a CSRF to Stored XSS chain.

Explanation of Vulnerability in Simple Terms

02Summary

Xhanch – My Advanced Settings versions 1.1.2 and earlier are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the administrator's knowledge. The vulnerability requires the victim to visit the attacker's page while authenticated.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or perform administrative actions if an admin visits a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Site admin must be logged in and visit an attacker-controlled webpage.

Key dates

06Disclosure timeline

March 21, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE