Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-12756 is a high-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Avaya Spaces. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 20th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-12756 is an HTML Injection vulnerability in Avaya Spaces that may allow disclosure of sensitive information or modification of the page content seen by the user. Published on 2025-02-11, it is linked to CWE-1287 (Improper Validation of Specified Index or Position) and CWE-79 (Cross-site Scripting). The vulnerability carries a CVSS v3.1 base score of 7.3 (AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N), indicating high severity with network vector, high attack complexity, privileged access requirements, user interaction, changed scope, high confidentiality and integrity impacts, and no availability impact.
Exploitation requires an attacker with high privileges (PR:H) to have network access (AV:N), perform a high-complexity attack (AC:H), and induce user interaction (UI:R). A successful attack could enable the privileged attacker to disclose sensitive information or modify page content viewed by targeted users, leveraging the changed scope (S:C) for high confidentiality (C:H) and integrity (I:H) effects.
The Avaya advisory provides details on mitigation, available at https://support.avaya.com/css/public/documents/101091836.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-51091
Vulnerability Data
An HTML Injection vulnerability in Avaya Spaces may have allowed disclosure of sensitive information or modification of the page content seen by the user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.1V1.4.2V2.1.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.
SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.
Output filtering can catch or sanitize unneutralized script content before it is served to users.
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 target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
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.
A.5.6 only promotes membership in groups to improve knowledge, receive alerts, and share information; it performs no action that stops XSS exploitation (or even the underlying neutralization defect) and is a pure dependency for other controls per the owner's labeling rule.