CVE-2026-63314

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

EUVD-2026-101951 ↗

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.
Slican IPx < 6.62.0100
fixed in 6.62.0100
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1670Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 17h 20msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+51h26m
0
+2h
+4h
+6h
+8h
+10h

description

Slican IPx WebCTI contains an SQL injection flaw in an administrative JSON endpoint; installations prior to 6.62.0100 are affected. An authenticated user who can access the service may cause unintended database queries through specially formed input.

mitigation

Upgrade Slican IPx to version 6.62.0100 or later. Restrict WebCTI access to trusted authenticated users until the update is deployed.

fixed in 6.62.0100

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%12th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 09: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-15 09:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-63314

{
  "etk_id": "ETK-2026-1670",
  "cve_id": "CVE-2026-63314",
  "display_id": "CVE-2026-63314",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-101951",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Slican IPx WebCTI",
  "summary": "Slican IPx WebCTI contains an SQL injection flaw in an administrative JSON endpoint; installations prior to 6.62.0100 are affected. An authenticated user who can access the service may cause unintended database queries through specially formed input.",
  "mitigation": "Upgrade Slican IPx to version 6.62.0100 or later. Restrict WebCTI access to trusted authenticated users until the update is deployed.",
  "vendor": "Slican",
  "product": "IPx",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.62.0100"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.62.0100"
      ],
      "package_name": "IPx",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1231,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.422116133333333,
  "t0_at": "2026-10-15T09:00:40.742000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T09:00:40.742000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:00:40.742000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63314"
    }
  }
}

published 2026-10-15 10:44Z
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.