Security readout for executives and security teams
Plain-English summary
berliCRM 1.0.24 has a SQL injection flaw that could let an unauthenticated remote attacker read, and potentially alter, CRM database information. CRM data often includes customer and sales records, so exposed systems should be prioritized for review. Public exploit information exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a high-priority application security issue if berliCRM 1.0.24 is present. The main business concern is unauthorized access to CRM data. Prioritize internet-facing instances first and assign ownership to application and database teams.
Technical view
CVE-2020-37006 is a CWE-89 SQL injection in berliCRM 1.0.24 involving the src_record parameter on the index.php endpoint via POST. CVSS 3.1 is 8.2, network exploitable, low complexity, no privileges or user interaction required, with high confidentiality and low integrity impact.
Likely exposure
Risk is highest for organizations running berliCRM 1.0.24, especially if the application is internet-accessible. The source bundle names only version 1.0.24 and provides no CPEs or broader affected-version range.
Exploitation context
ExploitDB is listed as a public exploit reference, increasing practical risk. The CVE is not marked as CISA KEV in the provided data, and no cited source confirms active exploitation.
Researcher notes
Evidence identifies a specific parameter-level SQL injection and a public exploit reference. The provided sources do not name a patch, fixed version, workaround, or active exploitation. Scope should not be expanded beyond berliCRM 1.0.24 without additional vendor evidence.
Mitigation direction
- Identify any berliCRM deployments and confirm whether version 1.0.24 is in use.
- Check crm-now GmbH or berliCRM guidance for fixed versions or vendor-recommended mitigations.
- Restrict external access to berliCRM until remediation status is confirmed.
- Review database and application logs for suspicious CRM queries or unusual data access.
- Ensure recent backups exist before applying vendor updates or configuration changes.
Validation and detection
- Inventory web applications for berliCRM and record exposed instances.
- Confirm the installed berliCRM version from administrative or deployment records.
- Check whether the application exposes index.php to untrusted networks.
- Review web logs for abnormal POST activity involving src_record.
- Validate remediation against vendor guidance after any update or configuration change.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-37006 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-48872CVE reference · exploit
- Vendor HomepageCVE reference · product
- VulnCheck Advisory: berliCRM 1.0.24 - 'src_record' SQL InjectionCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.