CVE-2026-3332
CSRF and Stored XSS in Xhanch My Advanced Settings Plugin
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xhanch | my_advanced_settings | to 1.1.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Xhanch - My Advanced Settings plugin for WordPress has a vulnerability known as Cross-Site Request Forgery (CSRF) in all versions up to and including 1.1.2. This vulnerability exists because the plugin's settings update handler function, `xms_setting()`, lacks nonce validation. As a result, an attacker can trick a site administrator into performing an unintended action, such as clicking a malicious link, which allows the attacker to modify plugin settings without authentication.
The settings that can be changed include the favicon URL, Google Analytics account ID, and various WordPress behavior toggles. Additionally, the `favicon_url` and `ga_acc_id` values are output on the front-end without proper escaping, which can lead to a chain of attacks from CSRF to Stored Cross-Site Scripting (XSS).
How can this vulnerability impact me? :
This vulnerability can allow an attacker to modify important plugin settings without authorization by tricking an administrator into clicking a malicious link. Changes to settings like the favicon URL and Google Analytics account ID can affect the website's appearance and analytics data.
Because the modified values are output on the front-end without escaping, this can lead to a Stored Cross-Site Scripting (XSS) attack, potentially allowing attackers to execute malicious scripts in the context of the website, which can compromise user data, session tokens, or perform other malicious actions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the Xhanch - My Advanced Settings plugin for WordPress to a version later than 1.1.2 where the nonce validation issue in the xms_setting() function is fixed.
Additionally, as a temporary measure, you can disable or restrict access to the plugin settings update handler to prevent unauthorized modification of settings.
Ensure that site administrators are aware of the risk of clicking on untrusted links that could trigger forged requests.