CVE-2026-104123

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

GHSA-m6q3-w82g-46vw ↗EUVD-2026-91164 ↗

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-408, permanent identifier
18d 09h 44msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+25h08m
0
+2h
+4h
+6h
+8h
+10h

description

Online Reviewer Management System 1.0 contains an SQL injection issue in its activity-management request handler. A remote attacker may be able to manipulate database queries without authenticating when the affected endpoint is network-accessible.

mitigation

Restrict unauthenticated access to the affected administrative request handler and limit exposure of the application to trusted 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.
–
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.33%24th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 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-10-02 02:45Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 02:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-408",
  "cve_id": "CVE-2026-104123",
  "display_id": "CVE-2026-104123",
  "ghsa_id": "GHSA-m6q3-w82g-46vw",
  "euvd_id": "EUVD-2026-91164",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Online Reviewer Management System",
  "summary": "Online Reviewer Management System 1.0 contains an SQL injection issue in its activity-management request handler. A remote attacker may be able to manipulate database queries without authenticating when the affected endpoint is network-accessible.",
  "mitigation": "Restrict unauthenticated access to the affected administrative request handler and limit exposure of the application to trusted networks. Apply a vendor-provided update when one is available; the evidence does not identify a fixed version.",
  "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.0033,
  "epss_percentile": 0.2462,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.56705765,
  "t0_at": "2026-10-02T02:45:13.229000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T02:45:13.229000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T02:45:13.229000+00:00",
      "url": "https://github.com/advisories/GHSA-m6q3-w82g-46vw"
    }
  }
}

published 2026-10-03 03:37Z
last change 2026-10-21 04:45Z

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.