dbcve.org
ExtremecontrolApplication · Extremenetworks

CVE-2025-6235

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 25.5.12 or later.
See remediation →
68/100
Remediation priority · Elevated
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
In ExtremeControl before 25.5.12, a cross-site scripting (XSS) vulnerability was discovered in a login interface of the affected application. The issue stems from improper handling of user-supplied input within HTML attributes, allowing an attacker to inject script code that may execute in a user's browser under specific interaction conditions. Successful exploitation could lead to exposure of user data or unauthorized actions within the browser context.

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

A stored cross-site scripting (XSS) vulnerability exists in the login interface of ExtremeControl before version 25.5.12. The vulnerability stems from improper sanitization of user-supplied input when rendered within HTML attributes, allowing attackers to inject malicious script code that executes in victim browsers upon specific interactions.

MitigationUpgrade ExtremeControl to version 25.5.12 or later to address the improper input validation in HTML attribute contexts.

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
ExtremecontrolApplication
Affected:< 25.5.12

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Determine the installed ExtremeControl version
    Access the ExtremeControl management interface or use the system administration commands to retrieve the ExtremeControl software version. This is typically found in the system info, about page, or version display within the ExtremeControl dashboard or CLI.
    Affected if The displayed version number is lower than 25.5.12 (for example, 25.5.10, 25.4.x, or earlier)
  2. Confirm the login interface is accessible
    Verify that the ExtremeControl login interface is accessible on the network. This is typically accessible via HTTPS on the management IP or hostname of the ExtremeControl engine.
    Affected if The login interface is exposed and reachable from the network, as this is where the XSS vulnerability exists
  3. Identify user-supplied input fields on the login page
    Examine the ExtremeControl login page HTML source or interact with input fields such as username, password, or other supplementary fields to understand what data is rendered back into HTML attributes.
    Affected if User-supplied input is reflected in the page without proper encoding, especially within HTML attribute contexts

The environment is affected if ExtremeControl version is below 25.5.12 and the login interface is accessible, as the vulnerability lies in improper sanitization of input rendered within HTML attributes on that interface.

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 25.5.12 or later
Fixed in 25.5.12
Interim mitigation

Upgrade ExtremeControl to version 25.5.12 or later to address the improper input validation in HTML attribute contexts.

Recommended fix Moderate confidence

25.5.12

  1. 1. Back up the current ExtremeControl configuration and database.
  2. 2. Download ExtremeControl version 25.5.12 or later from the Extreme Networks support portal at extreme-networks.my.site.com.
  3. 3. Review the upgrade guide for ExtremeControl to ensure all prerequisites are met.
  4. 4. Initiate the upgrade process according to the official documentation.
  5. 5. After upgrade completes, verify the application is operational.
  6. 6. Test the login interface to confirm the XSS vulnerability is resolved.
  7. 7. Validate that existing users can authenticate properly after the upgrade.
Caveat Review release notes for any changes to functionality or backward compatibility before upgrading

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

Fix this in Extremecontrol Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6235 — 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-2025-6235 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