Security readout for executives and security teams
Plain-English summary
CVE-2024-45932 is a reported cross-site scripting issue in Krayin CRM v1.3.0. A malicious organization name could cause script execution when a user views or edits that record. This could expose data, alter visible content, or affect the user’s session, depending on privileges and browser context.
Executive priority
Treat as a high-priority application security issue if Krayin CRM v1.3.0 is internet-facing or used by many internal staff. Prioritize inventory and vendor guidance first because the provided sources do not name a patch.
Technical view
The CVE describes CWE-79 in Krayin CRM v1.3.0 via the organization name field at /admin/contacts/organizations/edit/2. CVSS 3.1 is 7.1 High: network reachable, low complexity, user interaction required, scope changed, and low confidentiality, integrity, and availability impact.
Likely exposure
Organizations running Krayin CRM v1.3.0 are the primary concern. Exposure depends on whether untrusted users can create or modify organization names, and whether privileged users later view those records in the CRM interface.
Exploitation context
The source bundle includes a public researcher write-up. CISA KEV status is false, and no provided source states active exploitation. The attack requires a user interaction event, such as viewing affected CRM content.
Researcher notes
Evidence is limited to the CVE metadata and linked researcher report. The CVSS vector says PR:N and UI:R, but the described path is under /admin, so validate actual access requirements in the deployed application before rating local exposure.
Mitigation direction
Check Krayin CRM vendor or project guidance for a fixed release or official workaround.
Upgrade if an official patched version is available and applicable.
Restrict who can create or edit organization records.
Apply server-side input validation and context-aware output encoding for organization names.
Consider temporary access controls around affected admin CRM pages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.