# CVE-2023-53951: Ever Gauzy v0.281.9 JWT Authentication Weakness via HMAC Secret

> Attackers can exploit weak HMAC secrets to forge JWT tokens, gaining unauthorized administrative access to the Ever Gauzy application.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-qh83-9fpx-6f4r

## What is CVE-2023-53951?

CVE-2023-53951 is a critical vulnerability in ever gauzy, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ever Gauzy v0.281.9 contains a JWT authentication vulnerability that allows attackers to exploit weak HMAC secret key implementation. Attackers can leverage the exposed JWT token to authenticate and gain unauthorized access with administrative permissions.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2023-53951 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-53951 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53951 is a critical vulnerability in ever gauzy, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-53951 exists.

Affected product: ever gauzy. 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-53951/ (Markdown: https://insights.sbomify.com/CVE-2023-53951/index.md)
```

## Sources

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

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