netbox-data-flows has stored XSS in ObjectAlias names rendered inside DataFlow tables
An authenticated user who can create or edit ObjectAlias objects can store arbitrary HTML/JavaScript in an alias name. That payload is later rendered unescaped in DataFlow table views, causing a stored XSS when another user views the affected page.
The issue is caused by unsafe HTML generation in the plugin’s custom table column renderer.
Relevant code on main (bf96eac, same commit as origin/main at the time of review):
netbox_data_flows/models/objectaliases.py
ObjectAlias.name is user-controlled (CharField)ObjectAlias.__str__() returns self.name directlynetbox_data_flows/tables/dataflows.py
DataFlowTable.sources and DataFlowTable.destinations use ObjectAliasListColumnnetbox_data_flows/tables/columns.py
ObjectAliasListColumn.render() calls object_list_to_string(value.all(), linkify=True)netbox_data_flows/utils/helpers.py
object_list_to_string() builds raw anchor tags with:
mark_safe(separator.join(f'<a href="{o.get_absolute_url()}">{o}</a>' for o in objects))
The alias text ({o}) is inserted into HTML without escaping, then the whole string is marked safe. Because ObjectAlias.__str__() returns the user-supplied name, HTML/JS in the alias name is executed in the victim’s browser.
This affects any page rendering DataFlowTable, including at least:
DataFlowTableEnvironment:
netbox-data-flows installedSteps:
ObjectAlias and DataFlow.ObjectAlias with the following name:
<img src=x onerror=alert(document.domain)>
DataFlow so this alias is present in either sources or destinations.A simple path to trigger is the Data Flow list page. Any other page that renders DataFlowTable should also be tested.
This is a stored cross-site scripting vulnerability.
Impacted users:
DataFlow tablePossible impact:
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도 | 87.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 87.00 |
VPI 공식 vpi-v1 기준