Skip to main content
CVE-2024-12756VulnerabilityPublished Updated

CVE-2024-12756: Avaya Spaces · CWE-1287

Affects Avaya SpacesSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Avaya Avaya SpacesAffected
  • =0
Fixed in–

AI-suggested

1. Immediate monitoring of Avaya Spaces usage for unusual HTML content or unexpected page modifications is recommended to detect potential exploitation attempts. 2. Restrict privileges and enforce the principle of least privilege to minimize the number of users who can perform actions requiring high privileges, reducing the attack surface. 3. Educate users about the risks of interacting with suspicious content within Avaya Spaces, emphasizing caution with unexpected prompts or links. 4. Implement Content Security Policy (CSP) headers if possible within the Avaya Spaces environment to restrict the execution of injected scripts or HTML elements. 5. Coordinate with Avaya support or security teams to obtain patches or updates as soon as they become available and apply them promptly. 6. Consider deploying web application firewalls (WAF) with custom rules to detect and block HTML injection patterns targeting Avaya Spaces endpoints. 7. Conduct regular security assessments and penetration testing focused on collaboration platforms to identify and remediate similar vulnerabilities proactively.

Description

An HTML Injection vulnerability in Avaya Spaces may have allowed disclosure of sensitive information or modification of the page content seen by the user.

References

Community reviews

Loading reviews…