# CVE-2026-48540: Krayin CRM client-side template injection in lead title

Source: https://junglewise.ai/threats/cve-2026-48540-krayin-crm-through-2-2-6-contains-a-stored-client-side-template  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-48540 · Severity: medium · CVSS 5.4 · Published 2026-09-24

Krayin CRM is a customer relationship management system used to manage sales leads and customer interactions. Through version 2.2.6, authenticated users can inject malicious Vue.js template code into lead titles that executes as JavaScript when other users view those leads, allowing attackers to steal session data, modify content, or perform actions on behalf of victims. The vulnerability requires user authentication and victim interaction but affects all users who view a poisoned lead record.

Technologies: [Webkul Krayin CRM](https://junglewise.ai/threats/technologies/krayin-crm). Vendors: [Webkul](https://junglewise.ai/threats/vendors/webkul).

## Quick answers

**Is CVE-2026-48540 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-48540 being exploited in the wild.

**How severe is CVE-2026-48540?** Medium severity, with a CVSS score of 5.4, published 24 September 2026.

**Which products and versions are affected?** Webkul Krayin CRM through 2.2.6.

**Is there a fix for CVE-2026-48540?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-48540 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-48540?** Check whether you run Webkul Krayin CRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a stored client-side template injection (CSTI) in the lead title field that fails to escape or sanitize Vue.js template syntax before rendering in the blade template. An authenticated attacker can inject double-brace expressions like {{ "a".constructor.prototype.charAt.constructor("code")() }} which reach the Vue template compiler; this enables prototype chain traversal to invoke the Function constructor and execute arbitrary JavaScript in the application origin for every user viewing the affected lead. The fix is to add the v-pre directive to the vulnerable h1 element in leads/view.blade.php to prevent Vue template compilation.

## Affected products

- Webkul Krayin CRM through 2.2.6

## Timeline

- 2026-09-24: disclosed
- 2026-09-24: other: CVE-2026-48540 published

## References

- [https://github.com/aaronamran/CVE-Disclosures/tree/main/CVE-2026/CVE-2026-48540](https://github.com/aaronamran/CVE-Disclosures/tree/main/CVE-2026/CVE-2026-48540)
- [https://www.vulncheck.com/advisories/krayin-crm-stored-template-injection-xss-via-lead-title](https://www.vulncheck.com/advisories/krayin-crm-stored-template-injection-xss-via-lead-title)

## Related threats

- [Krayin CRM stored template injection in web form description](https://junglewise.ai/threats/cve-2026-48543-krayin-crm-through-2-2-6-contains-a-stored-client-side-template)
- [Krayin CRM stored client-side template injection via product name](https://junglewise.ai/threats/cve-2026-48542-krayin-crm-through-2-2-6-contains-a-stored-client-side-template)
- [Krayin CRM stored template injection in person name field](https://junglewise.ai/threats/cve-2026-48541-krayin-crm-through-2-2-6-contains-a-stored-client-side-template)
- [Webkul Krayin CRM stored XSS in activity creation](https://junglewise.ai/threats/cve-2026-36341-webkul-krayin-crm-stored-xss-in-activity-creation)
- [Webkul Krayin CRM SSRF in Webhook Creation](https://junglewise.ai/threats/cve-2026-38527-webkul-krayin-crm-ssrf-in-webhook-creation)