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."
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 1.9NVD modified 2026-10-26 22:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- https://github.com/maxsite/cms/
- https://github.com/maxsite/cms/commit/8a3946bd0a54bfb72a4d57179fcd253f2c550cd7
- https://github.com/maxsite/cms/releases/tag/v109
- https://github.com/wnaspy/CVE/blob/main/Report-%20Stored%20XSS-in-ushki-plugin-maxsite-cms.pdf.pdf
- https://vuldb.com/submit/796741
- https://vuldb.com/vuln/359596
- https://vuldb.com/vuln/359596/cti