CVE-2026-112238

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

GHSA-7f5c-qwp3-q85h ↗EUVD-2026-104867 ↗

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.
TYPO3 Extension "File manager" < 3.1.3
fixed in 3.1.3
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-2153Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 04h 38msince last run
1h 03mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h13m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

The TYPO3 File manager extension's file search can mishandle search input and alter database queries. An attacker able to submit searches through the affected functionality may read data from the database.

mitigation

Upgrade ameos/ameos_filemanager to version 3.1.3. Until upgraded, restrict access to the extension's file-search functionality to trusted users.

fixed in 3.1.3

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.44%37th percentile
agent run time
1h 03m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 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-20 09:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2153",
  "cve_id": "CVE-2026-112238",
  "display_id": "CVE-2026-112238",
  "ghsa_id": "GHSA-7f5c-qwp3-q85h",
  "euvd_id": "EUVD-2026-104867",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in TYPO3 File manager extension",
  "summary": "The TYPO3 File manager extension's file search can mishandle search input and alter database queries. An attacker able to submit searches through the affected functionality may read data from the database.",
  "mitigation": "Upgrade ameos/ameos_filemanager to version 3.1.3. Until upgraded, restrict access to the extension's file-search functionality to trusted users.",
  "vendor": "TYPO3",
  "product": "Extension \"File manager\"",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.1.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.1.3"
      ],
      "package_name": "ameos/ameos_filemanager",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0044,
  "epss_percentile": 0.3726,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 62.583634866666664,
  "t0_at": "2026-10-20T09:30:48.389000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T09:30:48.389000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T09:30:48.389000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112238"
    }
  }
}

published 2026-10-20 09:41Z
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.