# CVE-2020-36630: FreePBX cdr Cdr.class.php ajaxHandler sql injection

> An attacker with permissions can exploit SQL injection in the FreePBX CDR module's ajaxHandler to read or modify call detail records.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Dec 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cgmg-fw4f-9qc5

## What is CVE-2020-36630?

CVE-2020-36630 is a medium-severity SQL injection vulnerability in Sangoma Freepbx, published on 25 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in FreePBX cdr 14.0. It has been classified as critical. This affects the function ajaxHandler of the file ucp/Cdr.class.php. The manipulation of the argument limit/offset leads to sql injection. Upgrading to version 14.0.5.21 is able to address this issue. The name of the patch is f1a9eea2dfff30fb99d825bac194a676a82b9ec8. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216771.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-36630?

It affects 1 product.


Products: Sangoma Freepbx.

## How do I fix CVE-2020-36630?

No fix has been published for CVE-2020-36630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36630 being exploited?

There is no known exploitation of CVE-2020-36630 in the wild and no public exploit code.

## Other vulnerabilities in Sangoma Freepbx

- [CVE-2025-57819](https://insights.sbomify.com/CVE-2025-57819/): Sangoma FreePBX Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2019-19006](https://insights.sbomify.com/CVE-2019-19006/): Sangoma FreePBX Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-73663](https://insights.sbomify.com/CVE-2026-73663/): FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover (critical 9.3)
- [CVE-2026-73665](https://insights.sbomify.com/CVE-2026-73665/): FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and AMI action injection (critical 9.3)
- [CVE-2026-46376](https://insights.sbomify.com/CVE-2026-46376/): FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36630 and fix it if it is affected.

What it is: CVE-2020-36630 is a medium-severity SQL injection vulnerability in Sangoma Freepbx, published on 25 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36630 in the wild and no public exploit code.

Affected product: Sangoma Freepbx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36630/ (Markdown: https://insights.sbomify.com/CVE-2020-36630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36630
- OSV: https://osv.dev/vulnerability/CVE-2020-36630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36630/
Summaries are generated and may contain mistakes; the official description above is the record.