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-4499 Overview
CVE-2024-4499 is a Cross-Site Request Forgery (CSRF) vulnerability in the XTTS server component of parisneo/lollms version 9.6. The flaw stems from a lax Cross-Origin Resource Sharing (CORS) policy that allows cross-origin requests from arbitrary web pages. An attacker can trick an authenticated user into visiting a malicious page that issues unauthorized LoLLMS-XTTS API requests on the user's behalf. The affected API surface controls audio file reading and writing operations within the XTTS text-to-speech subsystem.
Critical Impact
When chained with other vulnerabilities, this CSRF flaw can be leveraged to read arbitrary files on the host system and write files outside the designated audio file directory.
Affected Products
- parisneo/lollms version 9.6
- LoLLMS-XTTS API server component
- Deployments exposing the XTTS server to user browsers
Discovery Timeline
- 2024-06-24 - CVE-2024-4499 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-4499
Vulnerability Analysis
The XTTS server shipped with parisneo/lollms 9.6 implements a permissive CORS policy that fails to restrict cross-origin requests to trusted origins. Because the server also accepts authenticated requests based on ambient browser context, any origin a victim visits can issue API calls to the local LoLLMS-XTTS endpoint. The vulnerability is classified under CWE-352: Cross-Site Request Forgery.
Successful exploitation gives attackers the ability to invoke audio file read and write operations through the XTTS API. The impact expands considerably when the CSRF is chained with path handling weaknesses in the same product, enabling arbitrary file read and file write outside the audio directory.
Root Cause
The underlying defect is an overly permissive CORS configuration on the XTTS HTTP server. The server does not validate the request origin and does not require anti-CSRF tokens for state-changing API endpoints. As a result, any JavaScript executing in a victim's browser can call the LoLLMS-XTTS API while the victim has access to the running service.
Attack Vector
An attacker hosts a malicious web page that issues cross-origin requests to the local LoLLMS-XTTS endpoint, typically bound to localhost. When a user running LoLLMS visits the page, the browser automatically forwards the requests without origin restriction. The attacker's page can then invoke XTTS endpoints to read audio files, overwrite audio files, or trigger additional file-system operations when combined with path traversal flaws in the same codebase. Technical details are documented in the Huntr Vulnerability Bounty report.
Detection Methods for CVE-2024-4499
Indicators of Compromise
- Unexpected audio files appearing or being modified in the LoLLMS XTTS audio output directory
- HTTP requests to the LoLLMS-XTTS API containing Origin or Referer headers from untrusted external domains
- Files written outside the configured audio file location on hosts running LoLLMS 9.6
Detection Strategies
- Inspect XTTS server access logs for cross-origin requests whose Origin header does not match the expected local or allow-listed origin
- Correlate browser navigation events with simultaneous API calls to the LoLLMS-XTTS endpoint from the same host
- Monitor file-system telemetry on the LoLLMS host for writes outside the designated audio directory tree
Monitoring Recommendations
- Enable verbose request logging on the XTTS server to capture full Origin, Referer, and endpoint information
- Alert on process creation chains where a browser process is followed by XTTS API traffic from a non-local source context
- Track version strings reported by LoLLMS instances to identify hosts still running the affected 9.6 release
How to Mitigate CVE-2024-4499
Immediate Actions Required
- Upgrade parisneo/lollms to a release later than 9.6 that restricts the XTTS CORS policy
- Restrict XTTS server network exposure to localhost or a trusted management network only
- Avoid browsing untrusted web content from any host that runs the LoLLMS XTTS server
Patch Information
No vendor advisory URL is listed in the NVD record. Users should consult the Huntr Vulnerability Bounty report and the upstream parisneo/lollms project for fixed releases beyond version 9.6.
Workarounds
- Configure a reverse proxy in front of the XTTS server that enforces a strict Access-Control-Allow-Origin allow-list
- Require an authentication token or custom header on all state-changing XTTS endpoints to break CSRF preconditions
- Bind the XTTS listener to 127.0.0.1 and use SSH tunneling for remote operator access instead of exposing the API to browsers
# Example reverse proxy CORS hardening (nginx)
location /xtts/ {
if ($http_origin !~* ^https?://(localhost|127\.0\.0\.1)(:[0-9]+)?$) {
return 403;
}
proxy_pass http://127.0.0.1:XTTS_PORT/;
}
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

