Adobe Connect versions 2025.3, 12.10 and earlier are affected by a reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser. Scope is changed.
Security readout for executives and security teams
Plain-English summary
An attacker can send a crafted link referencing a vulnerable Adobe Connect page. If clicked, the page may run attacker-controlled JavaScript as though it came from Adobe Connect, potentially exposing or altering limited browser-accessible information. Victim interaction is required, and the bundle reports no availability impact.
Executive priority
Prioritize within the normal vulnerability cycle, accelerating systems exposed to untrusted users or supporting sensitive meetings. This is not a critical outage risk, but reflected XSS can undermine trust in the Connect origin. Require version confirmation and remediation tracking because the supplied version fields are ambiguous.
Technical view
This remotely reachable reflected XSS (CWE-79) requires no privileges but does require user interaction. CVSS 3.1 is 6.1: low confidentiality and integrity impact, no availability impact, and changed scope. The description identifies Adobe Connect 2025.3, 12.10, and earlier as affected; structured version boundaries require vendor confirmation.
Likely exposure
Exposure exists where affected Adobe Connect releases are deployed and users can be induced to open attacker-supplied URLs. Risk is higher for externally reachable deployments and users with active Connect sessions. The bundle distinguishes Adobe Connect and Adobe Connect Desktop Application, but its version fields are not fully self-explanatory.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. Exploitation requires convincing a victim to visit a crafted URL referencing a vulnerable page. That requirement limits opportunistic automation, although trusted-origin script execution remains relevant to targeted attacks.
Researcher notes
The CVE reports changed scope and low confidentiality and integrity impact. Its narrative says 2025.3 and 12.10 or earlier; structured records show boundaries at 2025.9 and 12.11 with default unaffected. Treat this as release-track or record-format ambiguity and use APSB26-37 to confirm exact affected and corrected versions.
Mitigation direction
Inventory Adobe Connect server and desktop application versions, separating the 12.x and 2025.x release tracks.
Review APSB26-37 to identify and apply Adobe's applicable corrected release for each deployed product track.
Until remediation, consider limiting exposure of vulnerable pages and caution users about unsolicited Adobe Connect links.
Monitor relevant web and browser telemetry for suspicious crafted links or unexpected script execution.
Validation and detection
Confirm every Adobe Connect server and desktop installation, including unmanaged endpoints, against the vendor advisory.
Verify installed versions are outside Adobe's confirmed affected ranges for the appropriate release track.
Use approved, non-executing XSS checks to confirm untrusted reflected input is safely encoded.
Review logs and endpoint telemetry for suspicious Adobe Connect URLs or unexpected browser script activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.