CVE-2025-61949
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLogStare Collector contains a stored cross-site scripting vulnerability in UserManagement. If crafted user information is stored, an arbitrary script may be executed on the web browser of the user who logs in to the product's management page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLogStare Collector has a stored XSS vulnerability in its UserManagement module where malicious JavaScript can be embedded in user information fields (such as username, display name, or email). When other users log in and view the affected user management pages, the stored payload executes in their browser sessions, potentially allowing session hijacking or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LogStare Collector installation versionLocate the LogStare Collector installation and check its version number, typically found in the application header, about page, or installation directory metadataAffected if The installed version is Secuavaire Logstare Collector and is below 2.4.2
-
Verify UserManagement module accessibilityConfirm that the UserManagement or user administration interface is accessible in the web applicationAffected if The UserManagement module exists and is accessible to users
-
Inspect user information fields for embedded scriptsExamine all user records in the database or through the management interface, specifically checking username, display name, and email fields for any HTML script tags, javascript: URIs, or event handler attributesAffected if Any user record contains malicious JavaScript code (such as <script> tags, onload/onerror event handlers, or javascript: pseudo-protocol) in username, display name, or email fields
-
Verify stored payloads are renderableLog in with a different user account and navigate to the user management pages to observe if embedded content executes or renders as raw HTML/JSAffected if Stored payloads in user fields execute or display as executable JavaScript when viewed by other users
A user is affected if LogStare Collector version is below 2.4.2 AND the UserManagement module contains malicious script payloads in user information fields that execute when viewed by other users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.2
Implement strict input validation and sanitization on all user information fields during storage, combined with proper output encoding when rendering user data in the management interface to prevent script execution.
2.4.2
- Download Logstare Collector version 2.4.2 or later from the official vendor website (www.logstare.com)
- Back up the current Logstare Collector configuration and data
- Install or upgrade to Logstare Collector version 2.4.2
- Verify the upgrade was successful by checking the version number
- Log in to the management page and confirm the UserManagement functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data