# CVE-2026-63646: CordysCRM MCP Form Configuration Endpoint Exposed to Anonymous Users

> Unauthenticated attackers can access CRM form configuration data, revealing the application data model to facilitate further attacks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-46p5-m7pq-82hm

## What is CVE-2026-63646?

CVE-2026-63646 is a medium-severity vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.2, GET /mcp/form/config/{formKey} calls McpController.getMcpField without authentication because ShiroFilter.addPublicPathFilters marks /mcp/** as anonymous and the controller has no permission annotation. An unauthenticated caller can obtain field names, types, required flags, default values, options, validation rules, and binding sources for CRM modules, allowing reconstruction of the application data model and more targeted attacks against other inputs. This issue is fixed in version 1.7.2.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-63646 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63646 and fix it if it is affected.

What it is: CVE-2026-63646 is a medium-severity vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 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-63646 exists.

Affected product: 1Panel-dev CordysCRM. 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-63646/ (Markdown: https://insights.sbomify.com/CVE-2026-63646/index.md)
```

## Sources

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

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