Krayin laravel-crm up to 2.2.6 Inbound Parse inbound-parse injection

Summaryinfo

A vulnerability has been found in Krayin laravel-crm up to 2.2.6 and classified as critical. This impacts an unknown function of the file /admin/mail/inbound-parse of the component Inbound Parse. Performing a manipulation results in injection. This vulnerability is known as CVE-2026-90944. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Krayin laravel-crm up to 2.2.6. It has been classified as critical. This affects an unknown part of the file /admin/mail/inbound-parse of the component Inbound Parse. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Krayin CRM through 2.2.6 exposes the POST /admin/mail/inbound-parse endpoint without authentication, allowing unauthenticated attackers to inject arbitrary emails into the CRM inbox. Attackers can supply crafted RFC 2822 messages with forged sender information and headers to insert emails with any subject and body, including replies to existing conversation threads.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-90944 since 09/14/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/14/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Customer Relationship Management System

Vendor

• Krayin

Name

• laravel-crm

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6

Website

• Product: https://github.com/krayin/laravel-crm/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion