How severe is CVE-2024-4839?

CVE-2024-4839 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2024-4839 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-4839?

CVE-2024-4839 affects Lollms Lollms-webui. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-4839?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-4839 have an EU (EUVD) identifier?

Yes. CVE-2024-4839 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-44421.

When was CVE-2024-4839 published?

CVE-2024-4839 was published on 2024-06-24 and last updated on 2026-06-17.

CVE-2024-4839

CVE-2024-4839 is a low-severity vulnerability in Lollms Lollms-webui with a CVSS 3.x base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: Low (CVSS 3.x base score 3.3)
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-44421
Weakness: CWE-352
Affected product: Lollms Lollms-webui
Published: 2024-06-24
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2024-4839?: 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.
How severe is CVE-2024-4839?: CVE-2024-4839 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2024-4839 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-4839?: CVE-2024-4839 affects Lollms Lollms-webui. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-4839?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-4839 have an EU (EUVD) identifier?: Yes. CVE-2024-4839 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-44421.
When was CVE-2024-4839 published?: CVE-2024-4839 was published on 2024-06-24 and last updated on 2026-06-17.

References

https://huntr.com/bounties/dcfc5a07-0427-42b5-a623-8d943873d7ff

Affected products (1)

cpe:2.3:a:lollms:lollms-webui:9.6:*:*:*:*:*:*:*

More vulnerabilities in Lollms Lollms-webui

CVE-2024-4267 — Critical (CVSS 9.8): A remote code execution (RCE) vulnerability exists in the parisneo/lollms-webui, specifically within the 'open_file'…
CVE-2024-1601 — Critical (CVSS 9.8): An SQL injection vulnerability exists in the `delete_discussion()` function of the parisneo/lollms-webui application,…
CVE-2024-4403 — High (CVSS 8.8): A Cross-Site Request Forgery (CSRF) vulnerability exists in the restart_program function of the parisneo/lollms-webui…
CVE-2024-1646 — High (CVSS 8.2): parisneo/lollms-webui is vulnerable to authentication bypass due to insufficient protection over sensitive endpoints.…
CVE-2024-1569 — High (CVSS 7.5): parisneo/lollms-webui is vulnerable to a denial of service (DoS) attack due to uncontrolled resource consumption.…
CVE-2024-5125 — High (CVSS 7.3): parisneo/lollms-webui version 9.6 is vulnerable to Cross-Site Scripting (XSS) and Open Redirect due to inadequate input…

All CVEs affecting Lollms Lollms-webui →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →