Insufficient HTML Sanitization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Affected versions can have malicious javascript code injected into the users browser by other authenticated users, as data fields retrieved from the database are not properly sanitized before displaying in various front-end views. The problem here stems from multiple issues: - Insufficient database sanitation on multiple fields allows injection of un-sanitized HTML - Lack of HTML escaping when rendering data on the front end The attack vector here is limited, as only authenticated users are able to write data to the database, for it to be subsequently rendered on the front-end. However, it is a vulnerability that the InvenTree development team takes seriously. Solution The proposed patch for this vulnerability is prevents injection of un-escaped fields into front-end UI elements. A future patch will also address sanitization of database fields on the "back end", however this will require a much larger effort to refactor multiple database tables. Patches - The issue is…

Published by the source

17 Jun 2022, 01:16 UTC

Last modified by the source

8 Dec 2024, 05:43 UTC

Source last checked

26 Oct 2026, 13:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rm89-9g65-4ffr

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rm89-9g65-4ffr

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

# Patch Next advisory brief: GHSA-rm89-9g65-4ffr

Advisory: Insufficient HTML Sanitization
IDs: GHSA-rm89-9g65-4ffr
Record: https://patchnext.com/advisories/ghsa-rm89-9g65-4ffr (revision 2, source checked 26 Oct 2026, 13:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: inventree 0.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI inventree: affected < 0.7.2; fixed in 0.7.2

## Suggested inspection (read-only)
- `python -m pip show inventree`: 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 inventree.
- 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-rm89-9g65-4ffr (OSV record GHSA-rm89-9g65-4ffr lists affected ranges: PyPI inventree >=0 <0.7.2 (fixed))
- Verified: https://github.com/advisories/GHSA-rm89-9g65-4ffr (GitHub-reviewed advisory GHSA-rm89-9g65-4ffr lists affected ranges: PyPI inventree >=0 <0.7.2)

Commands are suggestions: review each one before running it.