# CVE-2026-38526: File upload in n/a

> Authenticated attackers can upload malicious PHP files to the admin endpoint, leading to arbitrary code execution on the server.

- **Severity:** Critical 9.9 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-j8gj-mw5g-642g

## What is CVE-2026-38526?

CVE-2026-38526 is a critical vulnerability in n/a, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated arbitrary file upload vulnerability in the /admin/tinymce/upload endpoint of Webkul Krayin CRM v2.2.x allows attackers to execute arbitrary code via uploading a crafted PHP file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-38526 being exploited?

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

Public exploit code:

- CVE-2026-38526 | Krayin CRM v2.2.x Authenticated RCE - Unrestricted PHP File Upload via TinyMCE (github_poc): https://github.com/NathanHimself/CVE-2026-38526-PoC
- CVE-2026-38526 exploit for Krayin CRM v2.2.x - Authenticated RCE via TinyMCE file upload bypass. Features interactive shell, multi-type payloads, auto shell generation, and verification. Author: Sudeepa Wanigarathna. For authorized testing only. (github_poc): https://github.com/CerberusMrXi/KrayinCRM-RCE-Exploit-CVE-2026-38526
- Proof of Concept of CVE-2026-38526 in Krayin CRM <= v2.2.x. Arbitrary File Upload leading to Remote Code Execution (github_poc): https://github.com/pawpic/CVE-2026-38526-POC
- A PoC script for CVE-2026-38526, RCE via a file upload vulnerability in the /admin/tinymce/upload endpoint of webkul krayin 2.2.x (github_poc): https://github.com/Resolvdd/CVE-2026-38526-PoC-htb-nexus
- PoC and write-up for the HackTheBox "Nexus" privilege escalation: root-run Gitea template-sync service vulnerable to path traversal via forged Git objects. Educational use only. (github_poc): https://github.com/Shirouuu/Gitea-template-sync-Path-Traversal-Privilege-Escalation-CVE-2026-38526-
- CVE-2026-38526 - Authenticated RCE exploit for Krayin CRM <= 2.2.x. Upload arbitrary PHP via /admin/tinymce/upload and gain remote code execution. Python PoC for security researchers, CTF players and bug bounty hunters. Tested on HTB Nexus. (github_poc): https://github.com/MRdark-ops/CVE-2026-38526

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38526 is a critical vulnerability in n/a, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38526 exists.

Affected product: n/a. 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-38526/ (Markdown: https://insights.sbomify.com/CVE-2026-38526/index.md)
```

## Sources

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

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