What is the CVSS score of EUVD-2026-21320?

EUVD-2026-21320 has a CVSS 3.0 base score of 9.6 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for EUVD-2026-21320?

Yes, a public proof-of-concept exploit is available for EUVD-2026-21320. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate EUVD-2026-21320?

Within 24 hours: Identify all parisneo/lollms deployments and verify current versions-if running versions prior to 2.2.0, immediately isolate affected instances or disable the create_post/social feed functionality. Within 7 days: Upgrade to parisneo/lollms version 2.2.0 or later once released and validated in a test environment; if unavailable, escalate to vendor for patch timeline and consider temporary WAF rules to block POST requests to create_post endpoints. Within 30 days: Complete migration of all production instances to the patched version, conduct user notification for potential account compromise, and perform security audit of social post content already stored in the database.

Parisneo Lollms EUVD-2026-21320

Q: Which versions of Parisneo Lollms are affected by EUVD-2026-21320?

A critical stored cross-site scripting vulnerability in parisneo/lollms prior to version 2.2.0 allows unauthenticated attackers to inject malicious code through social post functionality, which…. A patch is available.

| CVE-2026-1115 CRITICAL

Cross-site Scripting (XSS) (CWE-79)

2026-04-10 @huntr_ai

GHSA-8wrq-fv5f-pfp2

XSS Parisneo Lollms Parisneo

9.6

CVSS 3.0 · Vendor: huntr_ai

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Craft malicious JavaScript in social post
Delivery

Submit via create_post function
Exploit

Store unvalidated payload in database
Execution

Render post in Home Feed
Impact

Execute JavaScript in victim browser

Vulnerability Assessment

Weakness	CWE CWE-79 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Output encoding, context-aware escaping MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Remote unauthenticated attacker creates a malicious post via the social feature in parisneo/lollms versions prior to 2.2.0. Victims viewing the Home Feed execute the injected JavaScript in their browsers. No special configuration required—exploitation succeeds against default installations.
Impact	Critical stored XSS in social posting feature allows unauthenticated attackers to inject persistent malicious scripts executed across all users including admins. High CVSS (9.6) reflects network accessibility, low complexity, and severe impact (session hijacking, account takeover). Wormable potential amplifies blast radius. Patch available in v2.2.0; prioritize immediate upgrade for all deployments.
Exploit ScenarioDerived	Attacker crafts malicious post containing JavaScript payload via network-accessible social feature (PR:N, AC:L). Payload stores in database unsanitized. When users view Home Feed, script executes in their browsers harvesting session tokens or credentials. Administrator exposure enables full platform compromise.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 10, 2026

Stored cross-site scripting in parisneo/lollms versions prior to 2.2.0 enables unauthenticated attackers to inject malicious JavaScript through unsanitized social post content in the create_post function. Injected scripts execute in victims' browsers when viewing the Home Feed, enabling account takeover, session hijacking, and wormable propagation across the platform. The CVSS vector indicates network-accessible exploitation requiring user interaction, with scope change allowing cross-domain impact. No public exploit identified at time of analysis, but low attack complexity increases weaponization risk.

RemediationAI

Vendor-released patch: version 2.2.0 resolves the vulnerability through input sanitization in the create_post function. Organizations should immediately upgrade to 2.2.0 or later via standard package management. Verify installation from official repository at https://github.com/parisneo/lollms. The specific remediation commit 9767b882dbc893c388a286856beeaead69b8292a implements output encoding for user-generated content. If immediate upgrade is infeasible, disable social posting features or implement web application firewall rules filtering script tags in POST request bodies to /social endpoints. Consult vendor advisory at https://huntr.com/bounties/099aa4fe-7165-4337-889c-3fb4f1aa71aa for additional context.

Affected VersionsENISA

parisneo/lollms unspecified <2.2.0

Affected Packages

pypi lollms fix: 2.2.0

euvd parisneo_lollms_unspecified fix: 2.2.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in pypi, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Root cause lies in direct assignment of user-controlled input to DBPost model within backend/routers/social/__init__.py without HTML entity encoding or content security policy enforcement. CWE-79 stored variant allows persistent payload delivery. Scope change (S:C) in CVSS vector indicates DOM trust boundary violation enabling attacks beyond the vulnerable component's security context.

Know when Parisneo Lollms gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (huntr_ai) PRIMARY 9.6 CRITICAL

AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Primary rating from Vendor (huntr_ai) · only source for this CVE.

CVSS VectorVendor: huntr_ai

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Apr 11, 2026 - 02:30 nvd

Patch available

CVE Published

Apr 10, 2026 - 06:23 nvd

CRITICAL 9.6

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical stored cross-site scripting vulnerability in parisneo/lollms prior to version 2.2.0 allows unauthenticated attackers to inject malicious code through social post functionality, which executes when other users view the Home Feed. This could result in account takeover, session hijacking, and self-propagating attacks across the platform, directly threatening user account security and data confidentiality.

Business Impact: Severe

Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable user-generated social post creation and Home Feed rendering until patch availability; (2) Implement input validation and HTML sanitization at the application layer for all user-submitted content; (3) Deploy Web Application Firewall rules to detect and block JavaScript injection patterns in POST parameters; (4) Enforce Content Security Policy headers to restrict inline script execution; (5) Require re-authentication and password reset for all users once patch is applied.

Threat Intelligence Overview

EPSS Score

0.0%

Top 86% exploitable

Threat Intel

1 sources

Exploit

POC

Public exploit code exists

Social Media

Sightings

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment GHSA POC (1) CIRCL

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.