Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-38526-Exploit — my version of an exploit for Krayin CRM v2.2.x - CVE-2026-38526 | Kitploit
Tools/GitHubGitHub/sh3llc0d3-0x15/cve-2026-38526-exploit
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration Testing
GitHubsh3llc0d3-0x15/cve-2026-38526-exploit

CVE-2026-38526-Exploit

my version of an exploit for Krayin CRM v2.2.x - CVE-2026-38526

View Repository
126 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    960
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    554
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    349
  • 4

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    343
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    323
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    295

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-38526 — Krayin CRM

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.

Overview

FieldDetails
ProductKrayin CRM
Reported affected versions2.2.x — verify against the vendor's advisory
Vulnerability classCWE-434 — Unrestricted Upload of File with Dangerous Type
Potential impactUpload of an unsafe file; server-side code execution may be possible under specific conditions
ImplementationPython 3, HTTPX, Beautiful Soup
Entry pointCVE-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.

Research Objective

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:

  • Does the application enforce server-side file-type validation?
  • Can an authenticated account upload a file outside the intended allowlist?
  • Where is the uploaded file stored, and how is it served?
  • Can the server execute uploaded content, or is it served as inert data?
  • What privileges and configuration conditions are required for impact?

An accepted upload alone does not establish remote code execution. The storage path, server behavior, execution configuration, and resulting impact must be verified independently.

Proof of Concept

The Python script implements an HTTP workflow intended to assess the upload behavior:

  1. Establish an HTTP client session.
  2. Submit authentication details to the application.
  3. Handle the login page's CSRF-related requirements.
  4. Submit a file-upload request to the relevant application endpoint.
  5. Inspect the HTTP response and any returned file-location information.

The script's output should be treated as an observation of the application's response, not as automatic proof of successful code execution.

Validation Criteria

For reproducible research, distinguish the following outcomes:

  • Authentication confirmed: the application establishes an authenticated session.
  • Upload accepted: the application accepts the request and reports a stored resource.
  • File accessibility confirmed: the uploaded resource can be retrieved as expected.
  • Execution impact confirmed: a safe, controlled test demonstrates server-side execution in the authorized lab.

Do not report the final outcome unless the corresponding test was actually performed.

Requirements

  • Python 3
  • An isolated, authorized Krayin CRM test instance
  • Test credentials for an account permitted to use the relevant functionality
  • Dependencies listed in requirements.txt

Install 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

Usage

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.

Technical Analysis

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.

Defensive Recommendations

  • Upgrade to a vendor-confirmed fixed release when available.
  • Enforce strict server-side validation of permitted file types.
  • Store uploads outside executable web roots where practical.
  • Disable script execution in upload directories.
  • Apply least-privilege permissions to the application and uploaded files.
  • Review upload-related logs and existing files for suspicious activity.
  • Add regression tests for invalid extensions, MIME mismatches, and unexpected file content.

Reproducibility Notes

For a complete technical report, record:

  • Exact application version and deployment configuration.
  • Lab setup and authentication role used.
  • Request and response evidence with secrets and session tokens redacted.
  • The observed upload behavior and resulting file location.
  • Whether file retrieval and server-side execution were separately verified.
  • Any differences between the expected and observed results.

Only include claims and evidence that you personally verified or clearly attribute findings to their original sources.

References

  • CVE record
  • Krayin CRM source repository
  • Exploit-DB reference
  • HTTPX documentation
  • CWE-434 — Unrestricted Upload of File with Dangerous Type

Disclaimer

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.

Download Tool