# CVE-2025-4378: Hardcoded Credentials in Ataturk University's ATA-AOF Mobile Application

> Attackers can bypass authentication and take over accounts in the Ataturk University ATA-AOF mobile app due to hardcoded credentials and cleartext transmission.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-m5ph-rhpp-mfxj

## What is CVE-2025-4378?

CVE-2025-4378 is a critical vulnerability in Ataturk University ATA-AOF Mobile Application, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cleartext Transmission of Sensitive Information, Use of Hard-coded Credentials vulnerability in Ataturk University ATA-AOF Mobile Application allows Authentication Abuse, Authentication Bypass.

This issue affects ATA-AOF Mobile Application: before 20.06.2025.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-4378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4378 is a critical vulnerability in Ataturk University ATA-AOF Mobile Application, published on 24 Jun 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-4378 in the wild and no public exploit code.

Affected product: Ataturk University ATA-AOF Mobile Application. 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-4378/ (Markdown: https://insights.sbomify.com/CVE-2025-4378/index.md)
```

## Sources

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

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