FusionPBX up to 4.5.7 call_broadcast_edit.php ID sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in FusionPBX up to 4.5.7. This impacts an unknown function of the file app\call_broadcast\call_broadcast_edit.php. This manipulation of the argument ID causes sql injection. This vulnerability is tracked as CVE-2019-16980. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in FusionPBX up to 4.5.7 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app\call_broadcast\call_broadcast_edit.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In FusionPBX up to v4.5.7, the file app\call_broadcast\call_broadcast_edit.php uses an unsanitized "id" variable coming from the URL in an unparameterized SQL query, leading to SQL injection.

The weakness was disclosed 10/21/2019. This vulnerability is known as CVE-2019-16980 since 09/29/2019. The attack can be launched remotely. The successful exploitation needs a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:app\call_broadcast\call_broadcast_edit.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-143980, VDB-143979, VDB-143981 and VDB-143978 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Patch: github.com

Timelineinfo

09/29/2019 🔍
10/21/2019 +22 days 🔍
10/21/2019 +0 days 🔍
01/17/2024 +1549 days 🔍

Sourcesinfo

Product: github.com

Advisory: 6fe372b3d4bb7ff07778d152886edcecc045c7ec
Status: Not defined

CVE: CVE-2019-16980 (🔍)
GCVE (CVE): GCVE-0-2019-16980
GCVE (VulDB): GCVE-100-143977
See also: 🔍

Entryinfo

Created: 10/21/2019 19:05
Updated: 01/17/2024 10:23
Changes: 10/21/2019 19:05 (36), 10/21/2019 20:58 (17), 01/17/2024 10:23 (5)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!