Every CVESearch/Get API key

GHSA-rm89-9g65-4ffr

Insufficient HTML Sanitization

No scoreFix available

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 addressed in the upcoming 0.8.0 release
  • This fix will also be back-ported to the 0.7.x branch, applied to the 0.7.2 release

Workarounds

There are no workarounds for this issue, users should upgrade to a patched version.

References

Thank you @saharshtapi for bringing this issue to our attention and giving pointers for fixing them.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in github
  • Email us at security@inventree.org

What each source reports

GitHub AdvisoriesNo score

Insufficient HTML Sanitization

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 addressed in the upcoming 0.8.0 release
  • This fix will also be back-ported to the 0.7.x branch, applied to the 0.7.2 release

Workarounds

There are no workarounds for this issue, users should upgrade to a patched version.

References

Thank you @saharshtapi for bringing this issue to our attention and giving pointers for fixing them.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in github
  • Email us at security@inventree.org
Record
GHSA-rm89-9g65-4ffr
Updated
2026-11-02
OSVNo score

Insufficient HTML Sanitization

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 addressed in the upcoming 0.8.0 release
  • This fix will also be back-ported to the 0.7.x branch, applied to the 0.7.2 release

Workarounds

There are no workarounds for this issue, users should upgrade to a patched version.

References

Thank you @saharshtapi for bringing this issue to our attention and giving pointers for fixing them.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in github
  • Email us at security@inventree.org
Record
GHSA-rm89-9g65-4ffr
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
inventree
PyPI
before 0.7.2
0.7.2
inventree
PyPI
before 0.7.2, plus listed versions
0.0.10.0.20.0.30.0.40.0.5
Show 17 moreShow less
0.0.60.0.70.0.80.0.90.1.00.1.10.1.20.1.30.1.40.2.40.3.10.3.20.4.40.6.00.6.10.7.00.7.1
0.7.2

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

GHSA-rm89-9g65-4ffr is a vulnerability with no CVSS score yet in inventree, published June 17, 2022. No source lists public exploit code. Fixed in inventree 0.7.2.

References

MoveEnter Open