CVE-2020-36630 json
FreePBX cdr Cdr.class.php ajaxHandler sql injection
published 3y ago modified 4mo ago also EUVD-2020-24085
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- sangoma freepbx 14.0.5.21
Is CVE-2020-36630 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 5.5 | CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- FreePBX cdr
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/FreePBX/cdr/commit/f1a9eea2dfff30fb99d825bac194a676a82b9ec8
patch, third-party-advisory
-
github.com
/FreePBX/cdr/releases/tag/release%2F14.0.5.21
patch, release-notes, third-party-advisory
-
vuldb.com
/?id.216771
vdb-entry, technical-description, permissions-required, third-party-advisory
-
vuldb.com
/?ctiid.216771
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2020-36630
- NVD CVE-2020-36630
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.