CVE-2026-36340
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in Krayin CRM v.2.1.5 and fixed in v.2.1.6 allows a remote attacker to execute arbitrary code via the compose email function
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKrayin CRM versions 2.1.5 and earlier contain a remote code execution vulnerability in the compose email function, allowing authenticated remote attackers to inject and execute arbitrary code. The vulnerability was patched in version 2.1.6.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Krayin CRM versionLocate the version file or admin panel version info. Typical paths include the composer.json file in the installation root, or the 'About' section in the admin dashboard. Run: cat composer.json | grep version or check the admin interface under System > Configuration > General > About.Affected if The installed version is 2.1.5 or any version lower than 2.1.6
-
Verify email compose functionality is accessibleLog in as an authenticated user and navigate to the email compose interface. This is typically found in the Email or Communications module. Confirm the compose/create email form is accessible and functional.Affected if The email compose feature is enabled and accessible to users in the current environment
-
Check for unauthorized email composition activityReview email logs, outgoing mail queues, or server access logs for suspicious email composition. Look for unexpected email records, unusually high volume, or emails containing attachments or links not initiated by legitimate users.Affected if There is any unauthorized or suspicious email composition activity in logs or mail queues
-
Inspect email-related configuration filesExamine configuration files in the Krayin installation directory related to email (e.g., config/mail.php, .env file settings). Check for any unexpected modifications or misconfigurations that could enable code injection.Affected if Email configuration files show unexpected modifications or allow code injection vectors
-
Review user access controls on email moduleCheck the user role permissions in the admin panel under Users > Roles or ACL settings. Verify which roles have access to the email compose function and whether unauthorized users have been granted this permission.Affected if Untrusted or unauthorized user roles have been granted access to the email compose functionality
You are affected if your Krayin CRM installation is version 2.1.5 or earlier AND the email compose feature is accessible to users in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Krayin CRM to version 2.1.6 or later. Until patched, restrict access to the email compose functionality to trusted users only and monitor for suspicious email composition activity.
Krayin CRM v.2.1.6
- Backup the current Krayin CRM v.2.1.5 installation and database
- Upgrade Krayin CRM to version 2.1.6 by following the official upgrade instructions
- Verify the upgrade was successful by logging in and testing the compose email function
- Ensure all extensions and customizations are compatible with v.2.1.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data