# CVE-2025-2311: Authentication Bypass in Sechard Information Technologies' SecHard

> Attackers can bypass authentication and harvest sensitive information due to improper credential handling and cleartext transmission in SecHard.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-cfc5-c899-6ww2

## What is CVE-2025-2311?

CVE-2025-2311 is a critical authentication bypass vulnerability in SecHard, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Use of Privileged APIs, Cleartext Transmission of Sensitive Information, Insufficiently Protected Credentials vulnerability in Sechard Information Technologies SecHard allows Authentication Bypass, Interface Manipulation, Authentication Abuse, Harvesting Information via API Event Monitoring.

This issue affects SecHard: before 3.3.0.20220411.

Weakness: CWE-648 (Incorrect Use of Privileged APIs), CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-2311 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2311 is a critical authentication bypass vulnerability in SecHard, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2311 in the wild and no public exploit code.

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

## Sources

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

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