Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-8112 Overview
CVE-2024-8112 is a reflected cross-site scripting (XSS) vulnerability [CWE-79] in thinkgem JeeSite 5.3. The flaw resides in the /js/a/login resource within the Cookie Handler component. Attackers can manipulate the skinName argument to inject arbitrary JavaScript that executes in a victim's browser session. The vulnerability is remotely exploitable without authentication or user privileges. Public disclosure of the exploit technique has occurred through VulDB and the project's Gitee issue tracker.
Critical Impact
Unauthenticated remote attackers can inject arbitrary scripts into the JeeSite login interface by abusing the skinName cookie-handling parameter, enabling session hijacking, credential theft, and client-side attacks against administrators.
Affected Products
- JeeSite 5.3.0
- thinkgem JeeSite Cookie Handler component
- Applications embedding the vulnerable /js/a/login endpoint
Discovery Timeline
- 2024-08-23 - CVE-2024-8112 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-8112
Vulnerability Analysis
The vulnerability is a reflected XSS flaw in the JeeSite rapid-development platform. JeeSite is a Java-based enterprise framework built on Spring Boot and MyBatis. The affected code path handles cookie values through the /js/a/login resource, which processes the skinName parameter without proper output encoding. When an attacker supplies a crafted skinName value, the client-side cookie handler reflects the payload into the Document Object Model (DOM). This allows arbitrary JavaScript execution in the context of the JeeSite origin. The attack requires no authentication and can be delivered through a crafted link or malicious third-party site.
Root Cause
The root cause is missing input sanitization and output encoding in the Cookie Handler logic that consumes the skinName argument. User-controlled input flows directly into a browser-interpreted context without HTML or JavaScript escaping. This matches the classic improper neutralization pattern described by [CWE-79].
Attack Vector
Exploitation occurs over the network. An attacker crafts a URL or forces a cookie value containing JavaScript into the skinName parameter. When a victim visits the login page or follows the crafted link, the injected script executes within the JeeSite application origin. Because the login interface handles authentication, successful injection can be used to steal credentials, hijack session tokens, or perform actions on behalf of the authenticated user. No code example is published by the vendor; see the Gitee Issue Discussion and VulDB entry #275633 for additional context.
Detection Methods for CVE-2024-8112
Indicators of Compromise
- HTTP requests to /js/a/login containing script tags, event handlers, or encoded JavaScript in the skinName parameter or associated cookie
- Cookie values with skinName= followed by angle brackets, javascript: URIs, or URL-encoded payloads such as %3Cscript%3E
- Unexpected outbound requests from client browsers to attacker-controlled domains originating from the JeeSite login page
Detection Strategies
- Deploy web application firewall (WAF) rules that inspect query strings and cookies on /js/a/login for XSS payload signatures
- Enable server-side logging of the skinName parameter and alert on non-alphanumeric values
- Review browser Content Security Policy (CSP) violation reports for inline script blocks originating from the login page
Monitoring Recommendations
- Correlate login-page access logs with downstream authentication anomalies such as session reuse from new geographies
- Monitor for suspicious administrator session activity following visits to crafted JeeSite URLs
- Ingest web server and WAF telemetry into a centralized analytics platform to identify repeated probing of the Cookie Handler endpoint
How to Mitigate CVE-2024-8112
Immediate Actions Required
- Inventory all JeeSite 5.3.0 deployments and restrict administrative access to trusted networks until patched
- Apply input validation at a reverse proxy or WAF layer to reject skinName values containing HTML metacharacters
- Rotate administrator credentials and invalidate active sessions if the login page may have been targeted
Patch Information
At the time of NVD publication no fixed version is referenced in the advisory data. Track the upstream project through the Gitee Issue Discussion for remediation updates and apply the vendor-released fix once available. Until then, treat JeeSite 5.3.0 instances as exposed.
Workarounds
- Configure a strict Content Security Policy that disallows inline scripts on the JeeSite login page
- Set the HttpOnly and SameSite=Strict flags on authentication cookies to reduce session theft impact
- Deploy WAF signatures that normalize and reject payloads containing <script, onerror=, or javascript: in the skinName parameter
# Example ModSecurity rule to block XSS payloads in the skinName parameter
SecRule REQUEST_URI "@beginsWith /js/a/login" \
"chain,phase:2,deny,status:403,id:1008112,msg:'CVE-2024-8112 JeeSite skinName XSS attempt'"
SecRule ARGS:skinName|REQUEST_COOKIES:skinName "@rx (?i)(<script|javascript:|onerror=|onload=)" "t:none,t:urlDecodeUni"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

