How severe is GHSA-v7qw-hx66-4w9x?

GHSA-v7qw-hx66-4w9x has a CVSS score of 8.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v7qw-hx66-4w9x?

GHSA-v7qw-hx66-4w9x affects the following packages: netbox-data-flows (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-v7qw-hx66-4w9x?

Update netbox-data-flows to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v7qw-hx66-4w9x is resolved across your whole dependency graph.

How do I detect GHSA-v7qw-hx66-4w9x in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for netbox-data-flows. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v7qw-hx66-4w9x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v7qw-hx66-4w9x?

O3 pinpoints whether GHSA-v7qw-hx66-4w9x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v7qw-hx66-4w9x actively exploited in the wild?

No public exploit code has been indexed for GHSA-v7qw-hx66-4w9x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-v7qw-hx66-4w9x published, and has it been updated?

GHSA-v7qw-hx66-4w9x was published on May 7, 2026 and was last updated on May 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-v7qw-hx66-4w9x

HIGH

netbox-data-flows has stored XSS in ObjectAlias names rendered inside DataFlow tables

Published

May 7, 2026

Updated

May 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍netbox-data-flows

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Details

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 directly
netbox_data_flows/tables/dataflows.py
- DataFlowTable.sources and DataFlowTable.destinations use ObjectAliasListColumn
netbox_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:

the main Data Flow list page
model tabs that reuse DataFlowTable

PoC

Environment:

NetBox with netbox-data-flows installed
No special plugin configuration required

Steps:

Log in as a user with permission to create or edit ObjectAlias and DataFlow.
Create a new ObjectAlias with the following name:
```
<img src=x onerror=alert(document.domain)>
```
Create or edit a DataFlow so this alias is present in either sources or destinations.
Log in as another user and open the Data Flow list page in the plugin UI.
The JavaScript executes when the table renders the alias list.

A simple path to trigger is the Data Flow list page. Any other page that renders DataFlowTable should also be tested.

Impact

This is a stored cross-site scripting vulnerability.

Impacted users:

any authenticated user who can view a page rendering the affected DataFlow table
especially higher-privileged NetBox users, because an attacker with lower privileges may target them by planting a malicious alias name

Possible impact:

session theft
execution of privileged actions in the victim’s session
exfiltration of data visible to the victim in NetBox

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`netbox-data-flows`	all versions	1.5.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for netbox-data-flows. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update netbox-data-flows to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v7qw-hx66-4w9x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v7qw-hx66-4w9x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v7qw-hx66-4w9x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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. ### Details 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 `

O3 Security · Impact-Aware SCA

Is GHSA-v7qw-hx66-4w9x in your dependencies?

O3 detects GHSA-v7qw-hx66-4w9x across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works