Podlove Podcast Publisher Plugin up to 2.5.3 on WordPress contributor_list_table.php orderby sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Podlove Podcast Publisher Plugin up to 2.5.3 on WordPress. This affects an unknown part of the file lib\modules\contributors\contributor_list_table.php. The manipulation of the argument orderby as part of Parameter leads to sql injection. This vulnerability is traded as CVE-2017-12949. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Podlove Podcast Publisher Plugin up to 2.5.3 on WordPress (WordPress Plugin). It has been rated as problematic. This issue affects some unknown functionality of the file lib\modules\contributors\contributor_list_table.php. The manipulation of the argument orderby as part of a Parameter 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 integrity. The summary by CVE is:
lib\modules\contributors\contributor_list_table.php in the Podlove Podcast Publisher plugin 2.5.3 and earlier for WordPress has SQL injection in the orderby parameter to wp-admin/admin.php, exploitable through CSRF.
The bug was discovered 08/07/2017. The weakness was shared 08/18/2017 (Website). The advisory is shared at defensecode.com. The identification of this vulnerability is CVE-2017-12949 since 08/18/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:lib\modules\contributors\contributor_list_table.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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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
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
08/07/2017 🔍08/18/2017 🔍
08/18/2017 🔍
08/18/2017 🔍
08/19/2017 🔍
11/08/2019 🔍
Sources
Advisory: defensecode.comStatus: Not defined
CVE: CVE-2017-12949 (🔍)
GCVE (CVE): GCVE-0-2017-12949
GCVE (VulDB): GCVE-100-105569
Entry
Created: 08/19/2017 08:55Updated: 11/08/2019 21:48
Changes: 08/19/2017 08:55 (60), 11/08/2019 21:48 (1)
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.