CVE-2026-7016
Description
A vulnerability was found in MaxSite CMS up to 109.3. Impacted is an unknown function of the component ushki Plugin. Performing a manipulation of the argument f_ushka_new/f_ushk results in cross site scripting. Remote exploitation of the attack is possible. The exploit has been made public and could be used. Upgrading to version 109.4 is recommended to address this issue. The patch is named 8a3946bd0a54bfb72a4d57179fcd253f2c550cd7. Upgrading the affected component is recommended. The vendor was informed early about this issue. They classify it as a "Self-XSS". They deployed a countermeasure: "Nevertheless, we consider this a violation of secure coding standards. The lack of filtering via htmlspecialchars() has already been fixed in the latest patch to prevent incorrect data display."
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Stored XSS in MaxSite CMS ushki plugin via unsanitized input (f_ushka_new/f_ushk) allows self-XSS; fixed in version 109.4.
Vulnerability
Overview
CVE-2026-7016 describes a cross-site scripting (XSS) vulnerability in the ushki plugin of MaxSite CMS up to version 109.3. The root cause is the lack of output encoding with htmlspecialchars() when rendering user-supplied values for the parameters f_ushka_new and f_ushk. This allows an attacker to inject arbitrary HTML or JavaScript code that is subsequently stored and displayed to other users [1][3].
Exploitation
To exploit this issue, an attacker must craft a malicious payload and submit it via the affected plugin’s input fields. Because the vulnerability is classified by the vendor as a “Self-XSS,” successful exploitation requires the attacker to trick a legitimate user into entering the payload in their own browser session (e.g., via social engineering). However, once stored, the injected script can execute in the context of any user who views the compromised content, potentially leading to further attacks if the victim is an administrator [2][3].
Impact
An attacker exploiting this flaw can execute arbitrary JavaScript in the browser of a user who accesses the affected page. This could enable theft of session cookies, redirection to malicious sites, or defacement. The CVSS v3 base score of 2.4 reflects the low severity due to the self-XSS nature and the need for user interaction; nonetheless, the vendor acknowledges it as a violation of secure coding standards [1][2].
Mitigation
The issue has been addressed in MaxSite CMS version 109.4. The fix, identified in commit 8a3946bd0a54bfb72a4d57179fcd253f2c550cd7, adds htmlspecialchars() to sanitize the f_logging_file parameter, which was one of the vulnerable fields [1][4]. Users are strongly advised to upgrade to version 109.4 or later to prevent exploitation.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
6News mentions
0No linked articles in our index yet.