dbcve.org
ConnectApplication · Adobe

CVE-2026-27245

CRITICAL · 9.3 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 12.11 / 2025.9.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Connect versions 2025.3, 12.10 and earlier are affected by a reflected Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this vulnerability to inject malicious scripts into a web page, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Adobe Connect versions 2025.3, 12.10 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected into web pages through user-supplied input that is immediately reflected in the server's response. An attacker must trick a victim into visiting a crafted URL or interacting with compromised content to execute the malicious payload, potentially hijacking sessions or gaining elevated account access. The CVSS 9.3 score and changed scope indicate the vulnerability can impact components beyond the vulnerable web application.

MitigationUpgrade Adobe Connect to a patched version beyond 2025.3 or 12.10, and implement input validation and output encoding on all user-supplied parameters as a defense-in-depth measure until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ConnectApplication
Affected:< 12.11
Connect Desktop ApplicationApplication
Affected:<= 2025.3< 2025.9.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Connect version
    Access the admin interface and navigate to the About section, or check the installer/registry for the installed version
    Affected if Version is 12.10 or earlier, or any version less than 12.11
  2. Check Adobe Connect Desktop Application version
    Open the desktop application and verify the version in Help > About, or check the installed program version on the system
    Affected if Version is 2025.3 or earlier, or less than 2025.9.15
  3. Verify web application accessibility
    Determine if the Adobe Connect web portal is accessible to users over the network
    Affected if The web application is exposed and accepts user-supplied input in URL parameters or form fields
  4. Review input-handling behavior
    Test if URL parameters or form inputs are reflected in the response without encoding by submitting test input like <script>alert(1)</script> in a non-production test environment
    Affected if User-supplied input is reflected in server responses without proper encoding

A user is affected if they run Adobe Connect versions below 12.11 or Adobe Connect Desktop Application versions below 2025.9.15 and the web application is accessible to end users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.11 / 2025.9.15 or later
Fixed in 12.112025.9.15
Interim mitigation

Upgrade Adobe Connect to a patched version beyond 2025.3 or 12.10, and implement input validation and output encoding on all user-supplied parameters as a defense-in-depth measure until patching is complete.

Recommended fix High confidence

Adobe Connect 12.11 (server) and Adobe Connect Desktop Application 2025.9.15+

  1. 1. Identify the current Adobe Connect server version by accessing the admin dashboard or checking the installer version
  2. 2. For Adobe Connect server: Upgrade to version 12.11 or later (the first fixed release for this vulnerability)
  3. 3. Identify the current Adobe Connect Desktop Application version by opening the application and checking 'Help' > 'About'
  4. 4. For Adobe Connect Desktop Application: Upgrade to version 2025.9.15 or later (or the latest available version which should contain the fix)
  5. 5. After upgrading, verify the fix by confirming the application version matches or exceeds the fixed releases
  6. 6. Clear browser cache and cookies to ensure no cached malicious scripts persist
  7. 7. Test that the Adobe Connect interface loads correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data