CVE-2026-94278

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

GHSA-rfmq-49f4-7xx9 ↗EUVD-2026-92968 ↗

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.
File Media Renamer <= 1.3
CWE-284 Improper Access Control
ETK-2026-734, permanent identifier
15d 05h 05msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

File Media Renamer through version 1.3 does not enforce ownership checks when renaming media attachments. An authenticated user with file-upload privileges can rename attachments belonging to other users, potentially disrupting site data that references the original file path.

mitigation

Disable the plugin or restrict file-upload privileges to fully trusted users until an updated release is available. Review attachment names and dependent site data for unexpected changes.

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.22%11th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 06:00Z
Δ 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

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.

  1. 2026-10-06 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-734",
  "cve_id": "CVE-2026-94278",
  "display_id": "CVE-2026-94278",
  "ghsa_id": "GHSA-rfmq-49f4-7xx9",
  "euvd_id": "EUVD-2026-92968",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization flaw in File Media Renamer attachment renaming",
  "summary": "File Media Renamer through version 1.3 does not enforce ownership checks when renaming media attachments. An authenticated user with file-upload privileges can rename attachments belonging to other users, potentially disrupting site data that references the original file path.",
  "mitigation": "Disable the plugin or restrict file-upload privileges to fully trusted users until an updated release is available. Review attachment names and dependent site data for unexpected changes.",
  "vendor": null,
  "product": "File Media Renamer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "File Media Renamer",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 5.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L",
  "epss_score": 0.0022,
  "epss_percentile": 0.1126,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.036250916666667,
  "t0_at": "2026-10-06T06:00:21.326000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T06:00:21.326000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T06:00:21.326000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94278"
    }
  }
}

published 2026-10-06 06:31Z
last change 2026-10-21 11:18Z

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.