EUVD-2026-14189
GHSA-4fcp-jxh7-23x8
GHSA-5cx5-wh4m-82fh
GHSA-642q-3cpq-v266
GHSA-cgcg-q9jh-5pr2
GHSA-h29g-q5c2-9h4f
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
The Xhanch - My Advanced Settings WordPress plugin (versions up to 1.1.2) contains a Cross-Site Request Forgery vulnerability in its settings update handler due to missing nonce validation, allowing unauthenticated attackers to modify plugin settings if they can trick an administrator into clicking a malicious link. The vulnerability is particularly dangerous because unescaped output of the favicon_url and ga_acc_id settings enables a CSRF-to-Stored XSS chain, where injected payloads persist and affect all site visitors. While no active exploitation in the wild has been confirmed in public records and the CVSS score of 4.3 is relatively low, the attack requires only user interaction and results in stored cross-site scripting on the front-end.
Technical ContextAI
The vulnerability exists in the xms_setting() function of the Xhanch - My Advanced Settings plugin (CPE: cpe:2.3:a:xhanch_studio:xhanch_–_my_advanced_settings:*:*:*:*:*:*:*:*), which handles WordPress administrative settings updates. The root cause is classified as CWE-352 (Cross-Site Request Forgery), a server-side authorization flaw where state-changing requests lack cryptographic tokens to verify legitimate user intent. WordPress provides nonce mechanisms (wp_verify_nonce() and wp_create_nonce()) to prevent CSRF, but the plugin's setting handler fails to implement this validation. The secondary impact stems from improper output escaping—the stored favicon_url and ga_acc_id values are rendered on the front-end without using WordPress escaping functions such as esc_url() or esc_attr(), creating a stored XSS pathway when CSRF is used to inject malicious content into these fields.
RemediationAI
Update the Xhanch - My Advanced Settings plugin to a version later than 1.1.2 if available from the plugin author. If no patched version exists, disable or uninstall the plugin immediately and consider using alternative WordPress settings management solutions. Site administrators should manually audit their favicon and Google Analytics settings to ensure no malicious payloads were injected during the vulnerability window. As a temporary mitigation if the plugin must remain active, implement Web Application Firewall rules to block POST requests to the plugin's settings handler endpoint, and restrict WordPress administrative access to known IP ranges. Additionally, enforce HTTP-only cookies and implement Content Security Policy headers to limit the impact of any stored XSS that may have already been injected. Refer to the Wordfence vulnerability report at https://www.wordfence.com/threat-intel/vulnerabilities/id/66dd73c5-1cf1-484e-b847-afe357fb2598?source=cve for patch status and additional updates.
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today