# CVE-2025-63212: Information disclosure in n/a

> Unauthenticated attackers can retrieve session IDs from public log files to hijack admin sessions on GatesAir Flexiva-LX devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-mcxq-f773-jv28

## What is CVE-2025-63212?

CVE-2025-63212 is a medium-severity vulnerability in n/a, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GatesAir Flexiva-LX devices on firmware 1.0.13 and 2.0, including models LX100, LX300, LX600, and LX1000, expose sensitive session identifiers (sid) in the publicly accessible log file located at /log/Flexiva%20LX.log. An unauthenticated attacker can retrieve valid session IDs and hijack sessions without providing any credentials. This attack requires the legitimate user (admin) to have previously closed the browser window without logging out.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-63212?

It affects 4 products.


Products: Gatesair Flexiva Lx1000 Firmware, Gatesair Flexiva Lx100 Firmware, Gatesair Flexiva Lx300 Firmware, Gatesair Flexiva Lx600 Firmware.

## How do I fix CVE-2025-63212?

No fix has been published for CVE-2025-63212 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63212 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63212 and fix it if it is affected.

What it is: CVE-2025-63212 is a medium-severity vulnerability in n/a, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63212 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63212/ (Markdown: https://insights.sbomify.com/CVE-2025-63212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63212
- OSV: https://osv.dev/vulnerability/CVE-2025-63212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63212/
Summaries are generated and may contain mistakes; the official description above is the record.