CVE-2025-32370
Kentico Xperience ≤ 13.0.178
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:LSummary
CVE-2025-32370 is a high-severity Hidden Functionality (CWE-912) vulnerability in Kentico Xperience. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked in the top 29% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-9930
Vulnerability Data
Kentico Xperience before 13.0.178 has a specific set of allowed ContentUploader file extensions for unauthenticated uploads; however, because .zip is processed through TryZipProviderSafe, there is additional functionality to create files with other extensions. NOTE: this is a separate issue not…
more
necessarily related to SVG or XSS.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent introduction of undocumented hidden functionality during development.
Pre-acquisition integrity/authenticity checks can detect undocumented hidden functions in supplied software/hardware.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.