# CVE-2023-6960: CVE-2023-6960

> Attackers can retain access to smart locks after intended key deletion because the application only removes virtual keys on the client side.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 15 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-7r6g-j6cj-hx8v

## What is CVE-2023-6960?

CVE-2023-6960 is a high-severity vulnerability in Sciener TTLock App, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TTLock App virtual keys and settings are only deleted client side, and if preserved, can access the lock after intended deletion.

## Which versions are affected by CVE-2023-6960?


## How do I fix CVE-2023-6960?

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

## Is CVE-2023-6960 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6960 and fix it if it is affected.

What it is: CVE-2023-6960 is a high-severity vulnerability in Sciener TTLock App, published on 15 Mar 2024. 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-2023-6960 in the wild and no public exploit code.

Affected product: Sciener TTLock App. 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-2023-6960/ (Markdown: https://insights.sbomify.com/CVE-2023-6960/index.md)
```

## Sources

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

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