CVE-2025-71177: LavaLite CMS <= 10.1.0 Stored XSS via Package Creation and Search
LavaLite CMS versions up to and including 10.1.0 contain a stored cross-site scripting vulnerability in the package creation and search functionality. Authenticated users can supply crafted HTML or JavaScript in the package Name or Description fields that is stored and later rendered without proper output encoding in package search results. When other users view search results that include the malicious package, the injected script executes in their browsers, potentially enabling session hijacking, credential theft, and unauthorized actions in the context of the victim.
Security readout for executives and security teams
Plain-English summary
LavaLite CMS is reported vulnerable to stored cross-site scripting in package creation and search. A logged-in user could save malicious script in package fields, causing it to run when another user views matching search results. This can support account misuse, data theft, or unauthorized actions in the victim's browser.
Executive priority
Treat as a moderate-priority application security issue. Prioritize systems with multiple CMS users, sensitive admin sessions, or externally reachable login portals. Escalate if vendor guidance confirms affected production versions or if suspicious package content is found.
Technical view
The reported flaw is CWE-79 stored XSS affecting LavaLite CMS up to 10.1.0, via unencoded Package Name or Description values rendered in package search results. CVSS v4.0 is 5.1. The bundle contains inconsistent affected-version metadata, so version exposure should be confirmed against vendor and advisory details.
Likely exposure
Exposure is most likely on LavaLite CMS deployments where authenticated users can create or edit packages and other users view package search results. The source bundle does not prove broad internet exposure or unauthenticated reachability.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source establishes active exploitation. Exploitation requires authenticated access and victim interaction by viewing affected search results.
Researcher notes
Do not assume a universal fix from the bundle. The description names versions through 10.1.0, while the affected metadata lists version 0 with default status unaffected. Validate against the CVE record, issue, and VulnCheck advisory before closing exposure.
Mitigation direction
Check LavaLite and advisory channels for a patched release or official workaround.
Restrict package creation and editing to trusted administrative users.
Ensure package Name and Description fields are output-encoded in search results.
Review and remove suspicious package names or descriptions containing markup or script-like content.
Consider session hardening and least-privilege controls for CMS users.
Validation and detection
Inventory LavaLite CMS deployments and record exact running versions.
Confirm whether package creation is available to low-privileged authenticated users.
Review package records for unexpected HTML, script-like content, or suspicious links.
Verify search results render package fields as encoded text, not executable markup.
Check audit logs for recent package creation or edits by unusual accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.