CVE-2026-102908

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

GHSA-jhwc-qr2h-5725 ↗EUVD-2026-89582 ↗

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 Online Reviewer Management System 1.0
ETK-2026-109, permanent identifier
1d 21h 09msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+464h06m
0
+2h
+4h
+6h
+8h
+10h

description

Online Reviewer Management System 1.0 is affected by SQL injection in processing of an ID argument at an assessment question-view endpoint. A remote attacker able to reach that endpoint may alter database queries.

mitigation

Restrict access to the affected administrative endpoint to trusted networks and administrators, and limit the database account's privileges. Apply a vendor update when available; no fixed version is recorded.

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.
–
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.26%17th percentile
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 02:45Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-09-30 02:45Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 02:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-109",
  "cve_id": "CVE-2026-102908",
  "display_id": "CVE-2026-102908",
  "ghsa_id": "GHSA-jhwc-qr2h-5725",
  "euvd_id": "EUVD-2026-89582",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Online Reviewer Management System",
  "summary": "Online Reviewer Management System 1.0 is affected by SQL injection in processing of an ID argument at an assessment question-view endpoint. A remote attacker able to reach that endpoint may alter database queries.",
  "mitigation": "Restrict access to the affected administrative endpoint to trusted networks and administrators, and limit the database account's privileges. Apply a vendor update when available; no fixed version is recorded.",
  "vendor": "SourceCodester",
  "product": "Online Reviewer Management System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Online Reviewer Management 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": 0.0026,
  "epss_percentile": 0.1706,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.26847225,
  "t0_at": "2026-09-30T02:45:11.795000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T02:45:11.795000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T02:45:11.795000+00:00",
      "url": "https://github.com/advisories/GHSA-jhwc-qr2h-5725"
    }
  }
}

published 2026-09-30 12:50Z
last change 2026-10-21 07: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.