cosenary Instagram-PHP-API up to 4.9.32 on WordPress example/success.php error_description cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in cosenary Instagram-PHP-API up to 4.9.32 on WordPress. This issue affects some unknown processing of the file example/success.php. Executing a manipulation of the argument error_description as part of Parameter can lead to cross site scripting. The identification of this vulnerability is CVE-2019-14470. The attack may be launched remotely. Furthermore, there is an exploit available.
Details
A vulnerability was found in cosenary Instagram-PHP-API up to 4.9.32 on WordPress (Social Network Software). It has been declared as problematic. This vulnerability affects an unknown code block of the file example/success.php. The manipulation of the argument error_description as part of a Parameter leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:
cosenary Instagram-PHP-API (aka Instagram PHP API V2), as used in the UserPro plugin through 4.9.32 for WordPress, has XSS via the example/success.php error_description parameter.
The weakness was shared 09/04/2019 as EDB-ID 47304 as not defined exploit (Exploit-DB). The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2019-14470 since 08/01/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1059.007.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:example/success.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.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47304). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 4.9.0
- 4.9.1
- 4.9.2
- 4.9.3
- 4.9.4
- 4.9.5
- 4.9.6
- 4.9.7
- 4.9.8
- 4.9.9
- 4.9.10
- 4.9.11
- 4.9.12
- 4.9.13
- 4.9.14
- 4.9.15
- 4.9.16
- 4.9.17
- 4.9.18
- 4.9.19
- 4.9.20
- 4.9.21
- 4.9.22
- 4.9.23
- 4.9.24
- 4.9.25
- 4.9.26
- 4.9.27
- 4.9.28
- 4.9.29
- 4.9.30
- 4.9.31
- 4.9.32
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.7
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
08/01/2019 🔍09/04/2019 🔍
09/04/2019 🔍
09/04/2019 🔍
09/05/2019 🔍
09/25/2025 🔍
Sources
Advisory: EDB-ID 47304Status: Not defined
CVE: CVE-2019-14470 (🔍)
GCVE (CVE): GCVE-0-2019-14470
GCVE (VulDB): GCVE-100-141244
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/05/2019 09:14Updated: 09/25/2025 02:30
Changes: 09/05/2019 09:14 (47), 08/12/2020 14:36 (19), 09/25/2025 02:30 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.