Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41597 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Eyoucms. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked in the top 29% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
EyouCms version 1.6.2 contains a reflected cross-site scripting vulnerability in the administrative component located at /admin/twitter.php?active_t. The flaw is tracked as CVE-2023-41597 and is classified under CWE-79 with a CVSS 3.1 base score of 6.1 reflecting network attack vector, low complexity, no required privileges, required user interaction, and changed scope that permits limited impacts to confidentiality and integrity.
An unauthenticated remote attacker can exploit the issue by supplying a malicious payload in the active_t parameter of a crafted URL. When an authenticated administrator visits the link, the injected script executes in the context of the EyouCms administrative interface, enabling actions such as session token theft or unauthorized configuration changes within the affected application.
The associated EPSS score has remained flat at 0.1149 with no material increase since disclosure, indicating limited observed exploitation interest to date. No public advisories or patches are detailed in the supplied references.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-46091
Vulnerability Data
EyouCms v1.6.2 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the component /admin/twitter.php?active_t.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.
Validates web inputs to reject script-related content that could produce XSS.
Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Training partially blocks XSS exploitation by making users less likely to click on malicious links delivering XSS payloads and by making developers more likely to add some defensive measures, but it does not stop the underlying code defect from being exploitable, consistent with the AT-2 vs CWE-79 blocks=partial calibration anchor.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw in third-party components. XSS is overwhelmingly a first-party code defect in custom web applications, which A.8.8's scanning of published advisories and component inventory does not reach; that is A.8.29's territory (SAST/DAST). A.8.8 finds XSS only where it has been published as a CVE in a third-party component (CMS plugins, libraries, etc.), which is a minority of the class.