| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Brandbugle. It has been declared as critical. Impacted is an unknown function of the file /main.php. Such manipulation leads to sql injection. This vulnerability is documented as CVE-2020-36536. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in Brandbugle (version now known). It has been rated as critical. Affected by this issue is some unknown processing of the file /main.php. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The weakness was released 07/04/2020 by Mostafa Farzaneh. This vulnerability is handled as CVE-2020-36536. The attack may be launched remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
By approaching the search of inurl:main.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.
Once again VulDB remains the best source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/04/2020 🔍08/17/2020 🔍
06/03/2022 🔍
Sources
Researcher: Mostafa FarzanehStatus: Not defined
CVE: CVE-2020-36536 (🔍)
GCVE (CVE): GCVE-0-2020-36536
GCVE (VulDB): GCVE-100-159956
Entry
Created: 08/17/2020 08:09Updated: 06/03/2022 20:44
Changes: 08/17/2020 08:09 (32), 08/17/2020 08:14 (1), 06/03/2022 20:44 (3)
Complete: 🔍
Submitter: pyweb-security
Cache ID: 216::103
Submit
Accepted
- Submit #186: Brandbugle – SQL Injection vulnerability (by pyweb-security)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.