CVE-2026-103766

waiting for further signals

GHSA-29w7-pp39-xf4w ↗EUVD-2026-91138 ↗

no check availablenot proven exploitable

cve.orgpublic poc+0mkev

MacWarrior clipbucket-v5 >= 0, <= 5.5.3-#197

CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

ETK-2026-297, permanent identifier

cvss8.6cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

19d 13h 37msince last run

50mAI analysis

timeline

0 = cve.org publication

trigger signal (cve.org) +0hpublic poc+0hwaiting for further signals+5h59m

+2h

+4h

+8h

+10h

+12h

description

ClipBucket v5 through 5.5.3-#197 is affected by an SQL injection flaw in its advertising-management administration functionality. An attacker with an authenticated account granted ad_manager_access may read sensitive account data or alter and remove database records.

mitigation

Revoke ad_manager_access from accounts that do not require advertising administration and limit access to the administrative interface to trusted users and networks. Apply an upstream patched release when one is published; no fixed version is recorded in the advisory.

check

exploit

automation

contextual

auth required

yes, high privileges

EPSS

0.37%28th percentile

agent run time

50m

cve.org record, t = 0

2026-10-01 23:20Z

Δ to public poc

+0m

Δ to kev

–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

2026-10-01 23:20Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-103766
2026-10-11 23:33Z
exploit reference (hackmd.io)
cve_org · https://hackmd.io/@leediay/sqli-via-delete-ads-clipbucketv5

this entry in the feed

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

{
  "etk_id": "ETK-2026-297",
  "cve_id": "CVE-2026-103766",
  "display_id": "CVE-2026-103766",
  "ghsa_id": "GHSA-29w7-pp39-xf4w",
  "euvd_id": "EUVD-2026-91138",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated SQL injection in clipbucket-v5",
  "summary": "ClipBucket v5 through 5.5.3-#197 is affected by an SQL injection flaw in its advertising-management administration functionality. An attacker with an authenticated account granted ad_manager_access may read sensitive account data or alter and remove database records.",
  "mitigation": "Revoke ad_manager_access from accounts that do not require advertising administration and limit access to the administrative interface to trusted users and networks. Apply an upstream patched release when one is published; no fixed version is recorded in the advisory.",
  "vendor": "MacWarrior",
  "product": "clipbucket-v5",
  "affected": [
    {
      "affected_notes": [
        ">= 0, <= 5.5.3-#197"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "clipbucket-v5",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0037,
  "epss_percentile": 0.289,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 49.506511716666665,
  "t0_at": "2026-10-01T23:20:00.160000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-01T23:20:00.160000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T23:20:00.160000+00:00",
      "url": "https://hackmd.io/@leediay/sqli-via-delete-ads-clipbucketv5"
    },
    "trigger_signal": {
      "at": "2026-10-01T23:20:00.160000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T23:20:00.160000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103766"
    }
  }
}

published 2026-10-02 04:29Z
last change 2026-10-21 17:47Z

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.