CVE-2026-116253

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

GHSA-64f7-jr64-mq39 ↗EUVD-2026-109685 ↗

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.
DedeCMS 5.7.118
ETK-2026-2648Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 45msince 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+3h48m
0
+2h
+6h
+8h
+10h
+12h

description

DedeCMS 5.7.118 is affected by a code-injection vulnerability in its advertisement-rendering functionality. A remote, unauthenticated attacker may be able to inject code by supplying a crafted aid argument to the affected endpoint.

mitigation

Restrict unauthenticated network access to DedeCMS, especially its advertisement-rendering endpoint, until the vendor provides and you can apply a corrected release. Monitor vendor advisories for 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.
–
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 09: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

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-26 09:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-26 09:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2648",
  "cve_id": "CVE-2026-116253",
  "display_id": "CVE-2026-116253",
  "ghsa_id": "GHSA-64f7-jr64-mq39",
  "euvd_id": "EUVD-2026-109685",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code injection in DedeCMS advertisement rendering",
  "summary": "DedeCMS 5.7.118 is affected by a code-injection vulnerability in its advertisement-rendering functionality. A remote, unauthenticated attacker may be able to inject code by supplying a crafted aid argument to the affected endpoint.",
  "mitigation": "Restrict unauthenticated network access to DedeCMS, especially its advertisement-rendering endpoint, until the vendor provides and you can apply a corrected release. Monitor vendor advisories for a fixed version.",
  "vendor": null,
  "product": "DedeCMS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.7.118"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DedeCMS",
      "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.24922573333333,
  "t0_at": "2026-10-26T09:30:05.471000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T09:30:05.471000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T09:30:05.471000+00:00",
      "url": "https://github.com/advisories/GHSA-64f7-jr64-mq39"
    }
  }
}

published 2026-10-26 12:42Z
last change 2026-10-26 17:10Z

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.