# CVE-2025-11290: CRMEB JWT HMAC Secret hard-coded key

> Attackers can exploit a hard-coded JWT HMAC secret in CRMEB to bypass authentication and potentially take over accounts.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-4mrh-386v-3qq4

## What is CVE-2025-11290?

CVE-2025-11290 is a medium-severity vulnerability in CRMEB, published on 5 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in CRMEB up to 5.6.1. This affects an unknown function of the component JWT HMAC Secret Handler. Such manipulation of the argument secret with the input default leads to use of hard-coded cryptographic key
 . It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is reported as difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2025-11290 being exploited?

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

## Other vulnerabilities in CRMEB

- [CVE-2025-25763](https://insights.sbomify.com/CVE-2025-25763/): SQL injection in n/a (critical 9.8)
- [CVE-2023-30185](https://insights.sbomify.com/CVE-2023-30185/): File upload in n/a (critical 9.8)
- [CVE-2020-21787](https://insights.sbomify.com/CVE-2020-21787/): File upload in n/a (critical 9.8)
- [CVE-2020-25466](https://insights.sbomify.com/CVE-2020-25466/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-21394](https://insights.sbomify.com/CVE-2020-21394/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11290 is a medium-severity vulnerability in CRMEB, published on 5 Oct 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-2025-11290 exists.

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

## Sources

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

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