dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-25350

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in skygroup Miti miti allows Reflected XSS.This issue affects Miti: from n/a through < 1.5.3.

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 confidence

A reflected Cross-site Scripting (XSS) vulnerability exists in the skygroup Miti application (versions prior to 1.5.3). The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web pages without proper encoding or validation.

MitigationImplement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML context. Consider using a security-focused encoding library and deploying the vendor patch (v1.5.3 or later).

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if skygroup Miti is installed
    Check your application inventory or look for the 'Miti' web application in your web server directories (common paths include /opt/skygroup/miti, /var/www/miti, or the application's deployment directory). Look for directories or files containing 'miti' in the name.
    Affected if The skygroup Miti application is present on the system
  2. Determine the installed version
    Locate the application's version file, about page, or check the application startup logs. Common version file locations include version.php, VERSION, or a config file within the Miti installation directory. Compare the version number to 1.5.3.
    Affected if The installed version is lower than 1.5.3 (e.g., 1.5.2, 1.5.0, 1.0.0, etc.)
  3. Verify the web interface is accessible
    Check if the Miti application exposes HTTP/HTTPS endpoints. Attempt to access the application's login page or main entry point via browser or curl command.
    Affected if The web interface is reachable and accepts user input through URL parameters or form fields
  4. Identify user input reflection points
    Review web application logs or use a browser to submit test input (such as a benign string like 'TEST<XSS>') through URL parameters, search fields, or form inputs. Observe if the input is reflected back in the response without encoding.
    Affected if User-supplied input is reflected in HTML responses without visible sanitization or encoding

You are affected if the skygroup Miti application is installed with a version prior to 1.5.3 and has an accessible web interface that reflects user input without encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML context. Consider using a security-focused encoding library and deploying the vendor patch (v1.5.3 or later).

Recommended fix Moderate confidence

Miti version 1.5.3

  1. 1. Backup your current Miti installation and database before proceeding with any upgrade.
  2. 2. Download the latest version of Miti (version 1.5.3 or later) from the official skygroup Miti repository or vendor source.
  3. 3. Replace the existing Miti files with the new version, preserving any custom configuration files if needed.
  4. 4. Verify that all application dependencies are compatible with version 1.5.3.
  5. 5. Test the upgraded application thoroughly, particularly the areas where the XSS vulnerability was reported (reflected XSS vectors).
  6. 6. Monitor application logs for any errors or unusual activity following the upgrade.
Caveat Review vendor release notes for version 1.5.3 to check for any breaking changes or deprecations that may affect your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25350 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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