CVE-2026-3332: CWE-352 Cross-Site Request Forgery (CSRF) in xhanch_studio Xhanch – My Advanced Settings
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.
AI Analysis
Technical Summary
CVE-2026-3332 describes a CSRF vulnerability in the Xhanch - My Advanced Settings WordPress plugin caused by missing nonce validation in the xms_setting() function. Attackers can exploit this by tricking administrators into submitting forged requests that modify plugin settings such as favicon URL and Google Analytics account ID. Because these values are rendered on the front-end without escaping, this can lead to a stored cross-site scripting (XSS) condition. The vulnerability affects all versions up to and including 1.1.2. The CVSS 3.1 base score is 4.3, reflecting a medium severity with no confidentiality or availability impact but with integrity impact via unauthorized setting changes.
Potential Impact
An attacker can cause an authenticated site administrator to unknowingly modify plugin settings via CSRF, potentially injecting malicious content through the favicon URL or Google Analytics account ID fields. This can lead to stored XSS on the front-end, impacting site visitors. There is no direct impact on confidentiality or availability. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links while logged into the WordPress admin panel and consider disabling or removing the vulnerable plugin if feasible. Implementing additional CSRF protections at the site level may help mitigate risk.
CVE-2026-3332: CWE-352 Cross-Site Request Forgery (CSRF) in xhanch_studio Xhanch – My Advanced Settings
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-3332 describes a CSRF vulnerability in the Xhanch - My Advanced Settings WordPress plugin caused by missing nonce validation in the xms_setting() function. Attackers can exploit this by tricking administrators into submitting forged requests that modify plugin settings such as favicon URL and Google Analytics account ID. Because these values are rendered on the front-end without escaping, this can lead to a stored cross-site scripting (XSS) condition. The vulnerability affects all versions up to and including 1.1.2. The CVSS 3.1 base score is 4.3, reflecting a medium severity with no confidentiality or availability impact but with integrity impact via unauthorized setting changes.
Potential Impact
An attacker can cause an authenticated site administrator to unknowingly modify plugin settings via CSRF, potentially injecting malicious content through the favicon URL or Google Analytics account ID fields. This can lead to stored XSS on the front-end, impacting site visitors. There is no direct impact on confidentiality or availability. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links while logged into the WordPress admin panel and consider disabling or removing the vulnerable plugin if feasible. Implementing additional CSRF protections at the site level may help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-27T14:44:29.840Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69be180ef4197a8e3b78432d
Added to database: 3/21/2026, 4:01:18 AM
Last enriched: 4/9/2026, 6:47:07 PM
Last updated: 4/30/2026, 7:14:41 PM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.