# CVE-2025-4053: Unauthorized creation of master key in Mifare Classic Be-Tech cards

> Attackers with a guest card can create a master key to unlock all building locks due to cleartext storage, requiring full system replacement.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 26 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-cg49-x3j6-7j3g

## What is CVE-2025-4053?

CVE-2025-4053 is a medium-severity vulnerability in Be-Tech Mifare Classic cards, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The data stored in Be-Tech Mifare Classic card is stored in cleartext. An attacker having access to a Be-Tech hotel guest Mifare Classic card can create a master key card that unlocks all the locks in the building. 

This issue affects all Be-Tech Mifare Classic card systems. To fix the vulnerability, it is necessary to replace the software, encoder, cards, and PCBs in the locks.

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

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


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

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

## Is CVE-2025-4053 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4053 is a medium-severity vulnerability in Be-Tech Mifare Classic cards, published on 26 May 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-4053 in the wild and no public exploit code.

Affected product: Be-Tech Mifare Classic cards. 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-4053/ (Markdown: https://insights.sbomify.com/CVE-2025-4053/index.md)
```

## Sources

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

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