CVE-2025-70515

waiting for further signalsZero needs more public information before it can validate it.

GHSA-rv7g-8hm9-h22g ↗EUVD-2025-211052 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Fanvil x7a n/a
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-1329Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 21h 08msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+128h35m
0
+2h
+4h
+6h
+8h
+10h

description

Fanvil x7a firmware 2.6.0.1182 has a reflected cross-site scripting issue in its device log component. An attacker may cause script to run in a browser that renders affected log content; a user must access that component for the attack to take effect.

mitigation

Restrict access to the device log component to trusted administrators and limit exposure to untrusted input and networks. Obtain and apply a vendor-provided firmware update when one is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.24%13th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 00:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2025-70515

{
  "etk_id": "ETK-2026-1329",
  "cve_id": "CVE-2025-70515",
  "display_id": "CVE-2025-70515",
  "ghsa_id": "GHSA-rv7g-8hm9-h22g",
  "euvd_id": "EUVD-2025-211052",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site scripting in Fanvil x7a device log component",
  "summary": "Fanvil x7a firmware 2.6.0.1182 has a reflected cross-site scripting issue in its device log component. An attacker may cause script to run in a browser that renders affected log content; a user must access that component for the attack to take effect.",
  "mitigation": "Restrict access to the device log component to trusted administrators and limit exposure to untrusted input and networks. Obtain and apply a vendor-provided firmware update when one is available.",
  "vendor": "Fanvil",
  "product": "Fanvil x7a",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 6.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
  "epss_score": 0.0024,
  "epss_percentile": 0.1361,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.413276633333334,
  "t0_at": "2026-10-07T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-70515"
    }
  }
}

published 2026-10-12 08:26Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.