# CVE-2026-1203: CRMEB JSON Token LoginServices.php remoteRegister improper authentication

> Remote attackers can bypass authentication in CRMEB by manipulating the uid argument in the JSON Token Handler, potentially taking 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:** 20 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-rj2q-p862-w9r3

## What is CVE-2026-1203?

CVE-2026-1203 is a medium-severity authentication bypass vulnerability in CRMEB, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in CRMEB up to 5.6.3. The impacted element is the function remoteRegister of the file crmeb/app/services/user/LoginServices.php of the component JSON Token Handler. Executing a manipulation of the argument uid can lead to improper authentication. The attack may be performed from remote. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-1203?

It affects 1 product.


Products: Crmeb Crmeb.

## How do I fix CVE-2026-1203?

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

## Is CVE-2026-1203 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1203 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-2026-1203 and fix it if it is affected.

What it is: CVE-2026-1203 is a medium-severity authentication bypass vulnerability in CRMEB, published on 20 Jan 2026. 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-2026-1203 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-2026-1203/ (Markdown: https://insights.sbomify.com/CVE-2026-1203/index.md)
```

## Sources

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

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