CVE-2026-25349
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in skygroup Loobek loobek allows Reflected XSS.This issue affects Loobek: from n/a through < 1.5.2.
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 confidenceReflected XSS vulnerability in skygroup Loobek allows attackers to inject malicious scripts into web pages through unsanitized user input. The improper neutralization of input during web page generation enables the execution of attacker-controlled JavaScript in the context of the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 if Loobek is deployedReview your web applications or software inventory for skygroup Loobek. Check application directories, deployment manifests, or running services for Loobek references.Affected if Loobek from skygroup is present in the environment
-
Determine installed Loobek versionLocate the version file, about page, or API endpoint that reveals the Loobek version. Common locations include a /version endpoint, a config file, or the application footer. Compare the version number to 1.5.2.Affected if Installed version is lower than 1.5.2 or version cannot be determined
-
Confirm web interface is accessibleAccess the Loobek web application URL and verify it loads. Identify pages that accept user input through query parameters, form fields, or URL paths.Affected if Web interface is accessible and accepts user-supplied parameters
-
Inspect input handling behaviorSubmit test input with special characters like <script>alert(1)</script> or javascript:alert(1) in URL parameters or form fields. Examine the response to see if the input is reflected back without encoding or if the browser executes the script.Affected if User input is reflected in the response without proper HTML encoding or is executed as script
The environment is affected if skygroup Loobek is running with a version lower than 1.5.2 and the web interface exposes parameters that reflect unsanitized user input back to the browser.
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 · scopedUpgrade to Loobek version 1.5.2 or later which contains the security patch. Alternatively, implement proper output encoding and input validation on all user-supplied parameters before rendering them in HTML.
Loobek version 1.5.2
- 1. Identify all deployed instances of Loobek version < 1.5.2 in your environment
- 2. Obtain Loobek version 1.5.2 or later from the official vendor distribution channel
- 3. Backup the current Loobek installation and database before upgrading
- 4. Apply the upgrade to each affected instance following standard upgrade procedures
- 5. Verify the upgrade was successful by checking the version number
- 6. Test the application functionality to ensure no regressions were introduced
- 7. Confirm the XSS vulnerability is remediated by reviewing vendor release notes or changelog for the security fix
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-2026-25349 — 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-2026-25349 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