Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.8amended

Cross-site Scripting (XSS) in mindsdb/mindsdb

CVE-2024-3575GHSA-93c5-rj2p-w52x

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI mindsdb

    Affected
    <= 23.6.3.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
  • CVE-2024-3575: 0.37% estimated exploitation activity in the next 30 days; percentile 31.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

When a user uploads a csv file that contains an javascript payload a Cross-site Scripting (XSS) is triggered when the file is viewed. This is true for both cloud version and OSS version.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-93c5-rj2p-w52x

  2. Revision 1 · created ·

    Published from osv record GHSA-93c5-rj2p-w52x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-3575

Advisory: Cross-site Scripting (XSS) in mindsdb/mindsdb
IDs: CVE-2024-3575, GHSA-93c5-rj2p-w52x
Record: https://patchnext.com/advisories/cve-2024-3575 (revision 2, source checked 26 Oct 2026, 13:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mindsdb: affected <= 23.6.3.1

## Suggested inspection (read-only)
- `python -m pip show mindsdb`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mindsdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-93c5-rj2p-w52x (OSV record GHSA-93c5-rj2p-w52x lists affected ranges: PyPI mindsdb >=0 <=23.6.3.1)
- Verified: https://github.com/advisories/GHSA-93c5-rj2p-w52x (GitHub-reviewed advisory GHSA-93c5-rj2p-w52x lists affected ranges: PyPI mindsdb >=0 <=23.6.3.1)

Commands are suggestions: review each one before running it.

Loading voting…