CVE-2026-96661

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

GHSA-4cfq-96xx-p72v ↗EUVD-2026-100784 ↗

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.
pasyuk Gmedia Photo Gallery <= 1.25.1
ETK-2026-1867Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 03h 26msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+78h30m
0
+2h
+4h
+6h
+8h
+10h

description

Gmedia Photo Gallery for WordPress versions through 1.25.1 are affected by an SQL injection flaw in a gallery request parameter. An unauthenticated remote attacker may use the exposed endpoint to obtain sensitive information from the WordPress database, without needing a WordPress login.

mitigation

Disable or remove Gmedia Photo Gallery on affected sites until the vendor provides an updated release. Restrict public access to the affected WordPress endpoint where operationally feasible.

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.45%38th percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 03:39Z
Δ 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-14 03:39Z
    ghsa: trigger signal, started the run
  2. 2026-10-14 03:39Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1867",
  "cve_id": "CVE-2026-96661",
  "display_id": "CVE-2026-96661",
  "ghsa_id": "GHSA-4cfq-96xx-p72v",
  "euvd_id": "EUVD-2026-100784",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Gmedia Photo Gallery",
  "summary": "Gmedia Photo Gallery for WordPress versions through 1.25.1 are affected by an SQL injection flaw in a gallery request parameter. An unauthenticated remote attacker may use the exposed endpoint to obtain sensitive information from the WordPress database, without needing a WordPress login.",
  "mitigation": "Disable or remove Gmedia Photo Gallery on affected sites until the vendor provides an updated release. Restrict public access to the affected WordPress endpoint where operationally feasible.",
  "vendor": "pasyuk",
  "product": "Gmedia Photo Gallery",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.25.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Gmedia Photo Gallery",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0045,
  "epss_percentile": 0.3808,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.1685068,
  "t0_at": "2026-10-14T03:39:59.163000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T03:39:59.163000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T03:39:59.163000+00:00",
      "url": "https://github.com/advisories/GHSA-4cfq-96xx-p72v"
    }
  }
}

published 2026-10-17 09:32Z
last change 2026-10-21 13:29Z

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.