Piwigo-Guest-Book up to 1.3.0 Navigation Bar guestbook.inc.php Start sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.9 | $0-$5k | 0.08 |
Summary
A vulnerability was found in Piwigo-Guest-Book up to 1.3.0. It has been rated as critical. This issue affects some unknown processing of the file include/guestbook.inc.php of the component Navigation Bar. The manipulation of the argument Start leads to sql injection. The identification of this vulnerability is CVE-2014-125053. There is no exploit available. It is recommended to upgrade the affected component. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability was found in Piwigo-Guest-Book up to 1.3.0 (Photo Gallery Software). It has been declared as critical. This vulnerability affects an unknown functionality of the file include/guestbook.inc.php of the component Navigation Bar. The manipulation of the argument start
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 weakness was disclosed 01/06/2023 as 0cdd1c388edf15089c3a7541cefe7756e560581d. The advisory is available at github.com. This vulnerability was named CVE-2014-125053. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
By approaching the search of inurl:include/guestbook.inc.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.3.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 0cdd1c388edf15089c3a7541cefe7756e560581d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
potential SQL injection
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Piwigo-Guest-Book 1.3.1
Patch: 0cdd1c388edf15089c3a7541cefe7756e560581d
Timeline
01/06/2023 🔍01/06/2023 🔍
01/06/2023 🔍
01/29/2023 🔍
Sources
Advisory: 0cdd1c388edf15089c3a7541cefe7756e560581dStatus: Confirmed
CVE: CVE-2014-125053 (🔍)
GCVE (CVE): GCVE-0-2014-125053
GCVE (VulDB): GCVE-100-217582
Entry
Created: 01/06/2023 23:49Updated: 01/29/2023 14:31
Changes: 01/06/2023 23:49 (46), 01/29/2023 14:29 (2), 01/29/2023 14:31 (28)
Complete: 🔍
Cache ID: 216:18B:103
No comments yet. Languages: en.
Please log in to comment.