Fibar Home Center Lite/Home Center 2/Home Center 3 up to 5.021.38 Proxy API inclusion of functionality from untrusted control sphere
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Fibar Home Center Lite, Home Center 2 and Home Center 3 up to 5.021.38. This vulnerability affects unknown code of the component Proxy API. Performing a manipulation results in inclusion of functionality from untrusted control sphere. This vulnerability is known as CVE-2020-36905. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability classified as critical has been found in Fibar Home Center Lite, Home Center 2 and Home Center 3 up to 5.021.38. This affects some unknown functionality of the component Proxy API. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. CWE is classifying the issue as CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
FIBARO System Home Center 5.021 contains a remote file inclusion vulnerability in the undocumented proxy API that allows attackers to include arbitrary client-side scripts. Attackers can exploit the 'url' GET parameter to inject malicious JavaScript and potentially hijack user sessions or manipulate page content.
The weakness was published by Gjoko Krstic as 48240. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2020-36905 since 12/23/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 5.021.0
- 5.021.1
- 5.021.2
- 5.021.3
- 5.021.4
- 5.021.5
- 5.021.6
- 5.021.7
- 5.021.8
- 5.021.9
- 5.021.10
- 5.021.11
- 5.021.12
- 5.021.13
- 5.021.14
- 5.021.15
- 5.021.16
- 5.021.17
- 5.021.18
- 5.021.19
- 5.021.20
- 5.021.21
- 5.021.22
- 5.021.23
- 5.021.24
- 5.021.25
- 5.021.26
- 5.021.27
- 5.021.28
- 5.021.29
- 5.021.30
- 5.021.31
- 5.021.32
- 5.021.33
- 5.021.34
- 5.021.35
- 5.021.36
- 5.021.37
- 5.021.38
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (VulnCheck): 🔒
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: Inclusion of functionality from untrusted control sphereCWE: CWE-829
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
12/23/2025 CVE reserved01/06/2026 Advisory disclosed
01/06/2026 VulDB entry created
01/06/2026 VulDB entry last update
Sources
Advisory: 48240Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2020-36905 (🔒)
GCVE (CVE): GCVE-0-2020-36905
GCVE (VulDB): GCVE-100-339705
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/06/2026 17:11Changes: 01/06/2026 17:11 (78)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.