Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 1.7amended

Django TomSelect incomplete escaping of dangerous characters in widget attributes

GHSA-785h-76cm-cpmf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-tomselect 2025.3.3), redeploy, then verify what is actually installed.

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
1.7 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:U · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary User supplied values passed through to certain attributes in form widgets are not fully escaped for potentially dangerous tokens, and in some cases are rendered in browser as valid html tags. Details Attributes passed to the widget (such as labelfield) containing <, , and similar tokens are not fully escaped. This results in some raw values reaching the widget, and rendering in part or fully. For example, a label of: "Test User <scriptI can pass this to the labelfield and it gets rendered</script" is rendered in the choices's label visually as "Test User " with the trailing space, and what appears as an un-executed script tag following it (which is visible when viewing source). The actual output rendered in the browser for this example is: <div role="option" data-value="63f205b6" class="item" data-ts-item=""Test User <scriptI can pass this to the labelfield and it gets rendered</script</div The script tags appears to be valid in Chrome dev tools, but doesn't appear execute…

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

    Amended from ghsa record GHSA-785h-76cm-cpmf

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-785h-76cm-cpmf

Agent brief

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

# Patch Next advisory brief: GHSA-785h-76cm-cpmf

Advisory: Django TomSelect incomplete escaping of dangerous characters in widget attributes
IDs: GHSA-785h-76cm-cpmf
Record: https://patchnext.com/advisories/ghsa-785h-76cm-cpmf (revision 3, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: django-tomselect 2025.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django-tomselect: affected < 2025.3.3; fixed in 2025.3.3

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on django-tomselect.
- 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-785h-76cm-cpmf (OSV record GHSA-785h-76cm-cpmf lists affected ranges: PyPI django-tomselect >=0 <2025.3.3 (fixed))
- Verified: https://github.com/advisories/GHSA-785h-76cm-cpmf (GitHub-reviewed advisory GHSA-785h-76cm-cpmf lists affected ranges: PyPI django-tomselect >=0 <2025.3.3)

Commands are suggestions: review each one before running it.

Loading voting…