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

> An attacker can intercept cleartext credentials from web admin cookies to gain unauthorized access to the switch.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-gcjj-c9q9-5q75

## What is CVE-2025-25613?

CVE-2025-25613 is a high-severity vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FS Inc S3150-8T2F 8-Port Gigabit Ethernet L2+ Switch, 8 x Gigabit RJ45, with 2 x 1Gb SFP, Fanless. All versions before 2.2.0D Build 135103 were discovered to transmit cookies for their web based administrative application containing usernames and passwords. These were transmitted in cleartext using simple base64 encoding during every POST request made to the server.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Fs S3150-8t2f Firmware.

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

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

## Is CVE-2025-25613 being exploited?

There is no known exploitation of CVE-2025-25613 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-25625](https://insights.sbomify.com/CVE-2025-25625/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25613 is a high-severity vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25613 in the wild and no public exploit code.

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-25613/ (Markdown: https://insights.sbomify.com/CVE-2025-25613/index.md)
```

## Sources

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

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