
my version of an exploit for Krayin CRM v2.2.x - CVE-2026-38526
A Python proof of concept for investigating the reported file-upload vulnerability affecting Krayin CRM 2.2.x.
This repository documents the vulnerability's reported behavior, an HTTP-based testing workflow, and defensive recommendations. Testing must be restricted to an isolated lab or a system for which explicit authorization has been granted.
| Field | Details |
|---|---|
| Product | Krayin CRM |
| Reported affected versions | 2.2.x — verify against the vendor's advisory |
| Vulnerability class | CWE-434 — Unrestricted Upload of File with Dangerous Type |
| Potential impact | Upload of an unsafe file; server-side code execution may be possible under specific conditions |
| Implementation | Python 3, HTTPX, Beautiful Soup |
| Entry point | CVE-2026-38526.py |
Severity: The existing project notes report a CVSS score of 9.9. Confirm the score and affected-version range against authoritative vulnerability records before treating them as independently verified.
The purpose of this project is to investigate file-upload handling in the TinyMCE-related functionality of the affected application.
The key security questions are:
An accepted upload alone does not establish remote code execution. The storage path, server behavior, execution configuration, and resulting impact must be verified independently.
The Python script implements an HTTP workflow intended to assess the upload behavior:
The script's output should be treated as an observation of the application's response, not as automatic proof of successful code execution.
For reproducible research, distinguish the following outcomes:
Do not report the final outcome unless the corresponding test was actually performed.
requirements.txtInstall dependencies:
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt
On Windows, activate the environment with:
.venv\Scripts\Activate.ps1
Review the available arguments first:
python CVE-2026-38526.py --help
Use the arguments documented by the script to configure your isolated lab target and test account. Do not point the PoC at public systems or third-party infrastructure without explicit authorization.
The relevant security boundary is the server-side upload validation process.
Client-supplied filenames, extensions, MIME types, and HTTP headers must not be trusted as proof that a file is safe. A secure implementation should validate uploads on the server, apply an explicit allowlist, inspect file contents where appropriate, generate safe storage names, and prevent uploaded content from being executed.
The practical impact depends on the application code, authentication permissions, storage location, web-server configuration, and whether uploaded content can be interpreted as executable code.
For a complete technical report, record:
Only include claims and evidence that you personally verified or clearly attribute findings to their original sources.
This project is intended for education, defensive validation, and authorized security research. The presence of a successful HTTP response does not, by itself, prove remote code execution. Verify all findings in a controlled environment and follow applicable laws and authorization boundaries.