CVE-2026-36341
XSS in Webkul Krayin CRM v2.1.5
Publication date: 2026-05-07
Last updated on: 2026-05-07
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| webkul | krayin_crm | 2.1.5 |
| webkul | krayin_crm | 2.1.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute malicious scripts in the browsers of administrators or users with higher privileges who view the injected content. This can lead to unauthorized actions such as stealing session cookies, performing actions on behalf of the user, or delivering further malware. Since the vulnerability affects the administrative interface, it can be exploited to target high-privilege users without requiring them to click on malicious links, by abusing normal workflow processes.
Can you explain this vulnerability to me?
CVE-2026-36341 is a Cross-Site Scripting (XSS) vulnerability in Webkul Krayin CRM version 2.1.5. It occurs because the application does not properly sanitize user-supplied input in the comment field during Activity creation at the /admin/activities/create endpoint. This allows an attacker to inject malicious scripts or HTML code that can be executed in the browsers of users who view the affected content.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves Cross-Site Scripting (XSS) through unsanitized user input in the comment field during Activity creation on the /admin/activities/create endpoint of Webkul Krayin CRM v2.1.5.
To detect this vulnerability, you can attempt to inject typical XSS payloads into the comment field and observe if the input is rendered without proper sanitization, leading to script execution.
- Use curl or similar HTTP clients to send a POST request with a test script payload to the vulnerable endpoint, for example:
- curl -X POST -d 'comment=<script>alert(1)</script>' https://yourcrm.example.com/admin/activities/create -c cookies.txt -b cookies.txt
- Then, check the response or the rendered page in a browser to see if the script executes or if the input is sanitized.
- Alternatively, use web vulnerability scanners that test for XSS on input fields, targeting the /admin/activities/create endpoint.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Webkul Krayin CRM to a version that includes the fix for this vulnerability.
The vulnerability was addressed by sanitizing user input to remove executable JavaScript from the comment field, as implemented in the pull request merged on December 23, 2025 (PR #2401).
If updating immediately is not possible, apply input sanitization or filtering on the comment field to remove scripts and event handlers before rendering.
Additionally, restrict access to the /admin/activities/create endpoint to trusted users and monitor for suspicious input or activity.