Parisneo/Lollms
Approved changes feed: RSS · Atom
cpe:2.3:a:parisneo:parisneo/lollms:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Parisneo (47ba7f99-dd62-5638-afc5-b468bbe8b724) |
|---|---|
| Product | Parisneo/Lollms (30fdcc7e-973c-561b-9717-fb7e40a1ebed) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-12228 |
vulnerable | 2026-07-29 00:23:32.201020 |
Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms
HIGH (8.7)
A stored cross-site scripting (XSS) vulnerability exists in the `POST /api/prompts/share` endpoint of parisneo/lollms (latest version). The endpoint stores attacker-controlled `prompt_content` into `DBDirectMessage.content` without server-side sanitization. When a victim opens the direct message (DM) thread, the message is rendered by the DM UI through `MessageContentRenderer`, which uses `v-html` to insert rendered HTML into the DOM. The frontend sanitizer, which is regex-based, fails to comprehensively sanitize attacker-controlled HTML, allowing malicious payloads to execute in the victim's browser context. This vulnerability enables any authenticated user to send a malicious prompt-share message to another user's inbox, leading to arbitrary JavaScript execution, authenticated actions as the victim, exposure of same-origin application data, and potential account takeover.
Published: 2026-07-18T20:36:36.906Z
Updated: 2026-07-20T15:12:16.917Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1163 |
vulnerable | 2026-06-08 07:47:14.412033 |
Insufficient Session Expiration in parisneo/lollms
MEDIUM (4.1)
An insufficient session expiration vulnerability exists in the latest version of parisneo/lollms. The application fails to invalidate active sessions after a password reset, allowing an attacker to continue using an old session token. This issue arises due to the absence of logic to reject requests after a period of inactivity and the excessively long default session duration of 31 days. The vulnerability enables an attacker to maintain persistent access to a compromised account, even after the victim resets their password.
Published: 2026-04-08T02:20:50.573Z
Updated: 2026-04-08T15:58:36.451Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1117 |
vulnerable | 2026-06-08 07:47:14.351423 |
Improper Access Control in parisneo/lollms
HIGH (8.2)
A vulnerability in the `lollms_generation_events.py` component of parisneo/lollms version 5.9.0 allows unauthenticated access to sensitive Socket.IO events. The `add_events` function registers event handlers such as `generate_text`, `cancel_generation`, `generate_msg`, and `generate_msg_from` without implementing authentication or authorization checks. This allows unauthenticated clients to execute resource-intensive or state-altering operations, leading to potential denial of service, state corruption, and race conditions. Additionally, the use of global flags (`lollmsElfServer.busy`, `lollmsElfServer.cancel_gen`) for state management in a multi-client environment introduces further vulnerabilities, enabling one client's actions to affect the server's state and other clients' operations. The lack of proper access control and reliance on insecure global state management significantly impacts the availability and integrity of the service.
Published: 2026-02-02T09:55:26.972Z
Updated: 2026-02-02T17:49:47.974Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1116 |
vulnerable | 2026-06-08 07:47:14.351125 |
Cross-site Scripting (XSS) in parisneo/lollms
HIGH (8.2)
A Cross-site Scripting (XSS) vulnerability was identified in the `from_dict` method of the `AppLollmsMessage` class in parisneo/lollms prior to version 2.2.0. The vulnerability arises from the lack of sanitization or HTML encoding of the `content` field when deserializing user-provided data. This allows an attacker to inject malicious HTML or JavaScript payloads, which can be executed in the context of another user's browser. Exploitation of this vulnerability can lead to account takeover, session hijacking, or wormable attacks.
Published: 2026-04-12T02:22:52.389Z
Updated: 2026-04-13T17:49:36.132Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1115 |
vulnerable | 2026-06-08 07:47:14.350639 |
Stored XSS in parisneo/lollms
CRITICAL (9.6)
A Stored Cross-Site Scripting (XSS) vulnerability was identified in the social feature of parisneo/lollms, affecting the latest version prior to 2.2.0. The vulnerability exists in the `create_post` function within `backend/routers/social/__init__.py`, where user-provided content is directly assigned to the `DBPost` model without sanitization. This allows attackers to inject and store malicious JavaScript, which is executed in the browsers of users viewing the Home Feed, including administrators. This can lead to account takeover, session hijacking, and wormable attacks. The issue is resolved in version 2.2.0.
Published: 2026-04-10T06:23:13.463Z
Updated: 2026-04-10T13:01:44.634Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1114 |
vulnerable | 2026-06-08 07:47:14.348962 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-0562 |
vulnerable | 2026-06-08 07:47:12.539338 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-0560 |
vulnerable | 2026-06-08 07:47:12.536351 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-0558 |
vulnerable | 2026-06-08 07:47:12.533458 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-6386 |
vulnerable | 2026-06-08 07:43:14.961300 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9597 |
vulnerable | 2026-06-08 07:00:28.292182 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-7058 |
vulnerable | 2026-06-08 06:58:21.125015 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6985 |
vulnerable | 2026-06-08 06:58:20.891830 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6982 |
vulnerable | 2026-06-08 06:58:20.887430 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6971 |
vulnerable | 2026-06-08 06:58:20.867293 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6581 |
vulnerable | 2026-06-08 06:58:19.933867 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6281 |
vulnerable | 2026-06-08 06:58:18.466955 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6139 |
vulnerable | 2026-06-08 06:58:17.926222 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6085 |
vulnerable | 2026-06-08 06:58:17.715704 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6040 |
vulnerable | 2026-06-08 06:58:17.279418 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5824 |
vulnerable | 2026-06-08 06:56:17.505322 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5443 |
vulnerable | 2026-06-08 06:56:16.040840 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4881 |
vulnerable | 2026-06-08 06:50:18.947654 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4499 |
vulnerable | 2026-06-08 06:50:17.864979 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4315 |
vulnerable | 2026-06-08 06:50:17.494683 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4078 |
vulnerable | 2026-06-08 06:50:16.981698 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3429 |
vulnerable | 2026-06-08 06:41:53.282945 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3121 |
vulnerable | 2026-06-08 06:41:52.527677 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-11302 |
vulnerable | 2026-06-08 06:23:49.330456 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.