Security Resilience

CVE-2026-15305

Published
14 July 2026
Modified
24 October 2026
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0025 17th percentile
Risk Priority 39 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-15305 is a medium-severity Insufficient Type Distinction (CWE-351) vulnerability in Typo3 CMS (inferred from references). Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Space after Filename (T1036.006); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Users were able to upload files with arbitrary MIME types to forms using FileUpload or ImageUpload elements with allowedMimeTypes configured. The restriction was not enforced server-side because the MimeTypeValidator was registered during form building before concrete form definition properties were…

more

applied, resulting in the validator never being added to the processing pipeline. This issue affects TYPO3 CMS versions 14.2.0-14.3.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1036.006 Space after Filename Stealth
Adversaries can hide a program's true filetype by changing the extension of a file.
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
T1699 Direct Prompt Injection Execution
Adversaries may input malicious prompts directly into an LLM’s user interface.
T1036.007 Double File Extension Stealth
Adversaries may abuse a double extension in the filename as a means of masquerading the true file type.
T1036.008 Masquerade File Type Stealth
Adversaries may masquerade malicious payloads as legitimate files through changes to the payload's formatting, including the file’s signature, extension, icon, and contents.
T1696.002 Avoid CAPTCHA Stealth
Adversaries may avoid CAPTCHA challenges by mimicking human behavior.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-30510Shared CWE-351
CVE-2026-41341Shared CWE-351
CVE-2025-65960Shared CWE-351
CVE-2024-4769Shared CWE-351
CVE-2025-32035Shared CWE-351
CVE-2024-45676Shared CWE-351
CVE-2025-54413Shared CWE-351
CVE-2023-2866Shared CWE-351
CVE-2025-47939Shared CWE-351
CVE-2025-54412Shared CWE-351

Affected Assets

Typo3
CMS
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.3

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Input validation can reject or correctly classify data whose type is ambiguous or incorrect, stopping the weakness at entry points.

Associating security and privacy attributes with objects supplies the mechanism needed to distinguish element types and enforce handling rules.

Information flow enforcement requires explicit rules that distinguish information types or categories before permitting transfer.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent type-distinction flaws during development while the control addresses the full lifecycle.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect type confusion vulnerabilities before deployment.

prevents

Secure coding standards directly address proper type distinction and validation to prevent type-related flaws.

References