CVE-2026-28516

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

GHSA-prmh-rp39-qc4m ↗EUVD-2026-9097 ↗

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.+258d
opendcim <= 23.04
ETK-2026-4305Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 39msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
cve.org publicationtrigger signal +8.4mowaiting for further signals+8.5mokev
0
+3mo
+6mo
+9mo

description

openDCIM 23.04 through commit 4467e9c4 is affected by SQL injection in configuration updates handled by install.php and container-install.php. An attacker able to access the affected handler can alter or run commands against the application's database; this normally requires application access, but deployments with improperly configured Docker authentication may expose it without meaningful authentication.

mitigation

Restrict network and web access to the installation handlers, and ensure Apache uses real authentication rather than a static REMOTE_USER setting. Limit database account privileges and apply an upstream correction using parameterized database queries when one is available; no fixed version is identified in the evidence.

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.
–
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-02-27 22:11Z
Δ 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.
+258d

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-02-27 22:11Z
  2. 2026-11-12
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-12 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4305",
  "cve_id": "CVE-2026-28516",
  "display_id": "CVE-2026-28516",
  "ghsa_id": "GHSA-prmh-rp39-qc4m",
  "euvd_id": "EUVD-2026-9097",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in openDCIM configuration updates",
  "summary": "openDCIM 23.04 through commit 4467e9c4 is affected by SQL injection in configuration updates handled by install.php and container-install.php. An attacker able to access the affected handler can alter or run commands against the application's database; this normally requires application access, but deployments with improperly configured Docker authentication may expose it without meaningful authentication.",
  "mitigation": "Restrict network and web access to the installation handlers, and ensure Apache uses real authentication rather than a static REMOTE_USER setting. Limit database account privileges and apply an upstream correction using parameterized database queries when one is available; no fixed version is identified in the evidence.",
  "vendor": "opendcim",
  "product": "opendcim",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 23.04"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "openDCIM",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.0445122,
  "t0_at": "2026-02-27T22:11:52.246000+00:00",
  "signals": {
    "kev": {
      "at": "2026-11-12T00:00:00+00:00",
      "days": 258,
      "is_lower_bound": false,
      "measured_at": "2026-02-27T22:11:52.246000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-28516"
    },
    "trigger_signal": {
      "at": "2026-11-12T00:00:00+00:00",
      "days": 257.07508974537035,
      "is_lower_bound": false,
      "measured_at": "2026-02-27T22:11:52.246000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-28516"
    }
  }
}

published 2026-11-12 18:44Z
last change 2026-11-13 03:49Z

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.