CVE-2026-116060

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

GHSA-g3pw-7xrc-hwcv ↗EUVD-2026-109555 ↗

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.
SourceCodester Performance Indicator System 1.0
ETK-2026-2610Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 19msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h29m
0
+4h
+6h
+8h
+10h
+12h

description

SourceCodester Performance Indicator System 1.0 is affected by SQL injection in the dealer-addition endpoint. A remote, unauthenticated attacker may manipulate database queries through the Contact input; no user interaction is indicated.

mitigation

Restrict access to the affected application and dealer-addition endpoint to trusted users and networks. Apply a vendor-provided update when one is available; the evidence does not identify a fixed version.

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.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-25 16:30Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-25 16:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-25 16:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2610",
  "cve_id": "CVE-2026-116060",
  "display_id": "CVE-2026-116060",
  "ghsa_id": "GHSA-g3pw-7xrc-hwcv",
  "euvd_id": "EUVD-2026-109555",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in SourceCodester Performance Indicator System",
  "summary": "SourceCodester Performance Indicator System 1.0 is affected by SQL injection in the dealer-addition endpoint. A remote, unauthenticated attacker may manipulate database queries through the Contact input; no user interaction is indicated.",
  "mitigation": "Restrict access to the affected application and dealer-addition endpoint to trusted users and networks. Apply a vendor-provided update when one is available; the evidence does not identify a fixed version.",
  "vendor": "SourceCodester",
  "product": "Performance Indicator System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Performance Indicator System",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.998216566666667,
  "t0_at": "2026-10-25T16:30:18.104000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T16:30:18.104000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T16:30:18.104000+00:00",
      "url": "https://github.com/advisories/GHSA-g3pw-7xrc-hwcv"
    }
  }
}

published 2026-10-25 18:43Z
last change 2026-10-25 22:05Z

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.