WP-DBManager up to 2.7.1 on WordPress Database Manager INSERT Statement File input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in WP-DBManager up to 2.7.1 on WordPress. This affects an unknown function of the component Database Manager. Executing a manipulation as part of INSERT Statement can lead to input validation (File). The identification of this vulnerability is CVE-2014-8336. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in WP-DBManager up to 2.7.1 on WordPress (WordPress Plugin). This vulnerability affects an unknown part of the component Database Manager. The manipulation as part of a INSERT Statement leads to a input validation vulnerability (File). The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality. CVE summarizes:
The "Sql Run Query" panel in WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress allows remote attackers to read arbitrary files by leveraging failure to sufficiently limit queries, as demonstrated by use of LOAD_FILE in an INSERT statement.
The bug was discovered 10/16/2014. The weakness was shared 01/05/2018 (oss-sec). The advisory is available at openwall.com. This vulnerability was named CVE-2014-8336 since 10/20/2014. The exploitation appears to be easy. The attack can be initiated remotely. A single authentication is necessary for exploitation. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 1177 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.7.2 eliminates this vulnerability.
The entry VDB-111393 is related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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
Name: FileClass: Input validation / File
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: WP-DBManager 2.7.2
Patch: github.com
Timeline
10/16/2014 🔍10/20/2014 🔍
01/05/2018 🔍
01/05/2018 🔍
01/06/2018 🔍
01/20/2023 🔍
Sources
Advisory: 7037fa8f61644098044379190d1d4bf1883b8e4aStatus: Not defined
Confirmation: 🔍
CVE: CVE-2014-8336 (🔍)
GCVE (CVE): GCVE-0-2014-8336
GCVE (VulDB): GCVE-100-111394
X-Force: 97694
See also: 🔍
Entry
Created: 01/06/2018 17:11Updated: 01/20/2023 09:32
Changes: 01/06/2018 17:11 (64), 12/28/2019 19:21 (1), 01/28/2021 17:25 (3), 01/20/2023 09:32 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.