CVE-2024-4839 json
CSRF in Servers Configurations in parisneo/lollms-webui
published 2y ago modified 4mo ago also EUVD-2024-44421
- cvss
- 4.4
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'Servers Configurations' function of the parisneo/lollms-webui, versions 9.6 to the latest. The affected functions include Elastic search Service (under construction), XTTS service, Petals service, vLLM service, and Motion Ctrl service, which lack CSRF protection. This vulnerability allows attackers to deceive users into unwittingly installing the XTTS service among other packages by submitting a malicious installation request. Successful exploitation results in attackers tricking users into performing actions without their consent.
Is CVE-2024-4839 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/dcfc5a07-0427-42b5-a623-8d943873d7ff referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 4.4 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- parisneo parisneo/lollms-webui
- parisneo lollms-webui
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
huntr.com
/bounties/dcfc5a07-0427-42b5-a623-8d943873d7ff
exploit, third-party-advisory
Sources
- CVE List CVE-2024-4839
- NVD CVE-2024-4839
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.