CVE-2025-71385: Netdata < 2.3.1 - Reflected Cross-Site Scripting via love Parameter in ilove.svg Endpoint
Netdata before 2.3.1 reflects the user-supplied love query parameter of the api/v2/ilove.svg and api/v3/ilove.svg endpoints verbatim into the generated SVG document (into a text element) without HTML or XML escaping, and serves the response with Content-Type image/svg+xml. An attacker can craft a URL such as /api/v2/ilove.svg?love=<script>...</script>; when a victim navigates to it the injected script executes in the victim browser in the origin of the Netdata instance (reflected cross-site scripting). These endpoints are registered with HTTP_ACL_NOCHECK and anonymous access and, because bearer-token protection is disabled by default, are reachable without authentication on a default Netdata agent. The issue was resolved by removing the ilove endpoint.
Security readout for executives and security teams
Plain-English summary
Netdata, a popular open-source server monitoring agent, had a flaw in a decorative endpoint that let attackers slip malicious code into a link. If an employee clicked the crafted link while the monitoring dashboard was reachable, the attacker's script would run inside the browser session as if it came from Netdata itself, potentially stealing data or hijacking the dashboard.
Executive priority
Medium priority. This is a browser-side scripting flaw, not remote server takeover, but it targets a monitoring tool that many teams expose broadly. Schedule the Netdata 2.3.1 upgrade in the next standard patch window and confirm dashboards are not publicly reachable.
Technical view
Netdata versions before 2.3.1 reflect the `love` query parameter of `/api/v2/ilove.svg` and `/api/v3/ilove.svg` verbatim into an SVG text element with `Content-Type: image/svg+xml`, without HTML or XML escaping. The endpoints use `HTTP_ACL_NOCHECK` and anonymous access, and bearer-token protection is off by default, so the reflected XSS is reachable unauthenticated. The fix removes the ilove endpoint entirely.
Likely exposure
Any Netdata agent below 2.3.1 with the HTTP API reachable to a user's browser is exposed. Because bearer-token auth is disabled by default, most self-hosted and internet-adjacent Netdata instances are vulnerable without authentication. Impact is scoped to the Netdata origin, but that origin often exposes host telemetry.
Exploitation context
No CISA KEV listing and no public exploitation reports are cited in the source bundle. CVSS 3.1 base is 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), requiring a victim to click a crafted URL. A VulnCheck third-party advisory and a public fix commit exist, so proof-of-concept material is discoverable, raising opportunistic-abuse risk.
Researcher notes
Classic reflected XSS via unescaped SVG text content served as image/svg+xml (CWE-79). Endpoint registration with HTTP_ACL_NOCHECK and default-off bearer auth removes the need for credentials, so user interaction is the only gating factor. Scope:Changed reflects execution in the Netdata origin. Watch for chained abuse against session cookies or API tokens stored in that origin; hunt logs for `love=` parameters containing `<`, `%3C`, or `script`.
Mitigation direction
Upgrade all Netdata agents to version 2.3.1 or later, which removes the vulnerable ilove endpoint.
Restrict Netdata HTTP API exposure to trusted networks or place it behind an authenticating reverse proxy.
Enable Netdata bearer-token protection so anonymous requests to API endpoints are rejected.
Block or filter requests to /api/v2/ilove.svg and /api/v3/ilove.svg at the WAF or proxy until upgrades complete.
Remind staff not to click unsolicited monitoring or dashboard links while awaiting patching.
Validation and detection
Inventory Netdata deployments and record installed versions via `netdata -v` or the agent info API.
Confirm patched hosts return 404 or no reflection for /api/v2/ilove.svg and /api/v3/ilove.svg requests.
Verify the fix commit f82554f is present in the running build or that the version is >= 2.3.1.
Review proxy, WAF, and access logs for prior requests to ilove.svg containing script or angle-bracket payloads.
Test that unauthenticated API calls are rejected once bearer-token protection is enabled.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.