CVE-2026-1115 parisneo CVE debrief

Who should care

Defenders responsible for parisneo/lollms deployments should assess exposure and prioritize upgrading to version 2.2.0 or later. They should review user-provided content handling and input sanitization within the `create_post` function in `backend/routers/social/__init__.py`. Additionally, defenders should consider the potential operational impacts, including account takeover, session hijacking, and wormable attacks, and plan accordingly.

Why it matters

A critical Stored Cross-Site Scripting (XSS) vulnerability in parisneo/lollms allows attackers to inject and store malicious JavaScript, leading to account takeover, session hijacking, and wormable attacks. Defenders should prioritize upgrading to version 2.2.0 or later and review user-provided content handling.

• Account takeover through malicious JavaScript execution
• Session hijacking via stored XSS
• Potential for wormable attacks through social feature exploitation
• Verification of user-provided content handling and input sanitization

Technical summary

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. The issue is resolved in version 2.2.0. Defenders should prioritize upgrading to version 2.2.0 or later and review user-provided content handling and input sanitization within the affected product.

Defensive priority

Defenders should prioritize upgrading to version 2.2.0 or later and review user-provided content handling.

Recommended defensive actions

• Upgrade to version 2.2.0 or later
• Review user-provided content handling
• Implement input sanitization
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

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. Evidence is limited to the supplied source corpus and CVE record. Defenders should verify user-provided content handling and input sanitization within the affected product.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.