social-networks-auto-poster-facebook-twitter-g Plugin admin.php?page=nxssnap-reposter&action=edit cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in social-networks-auto-poster-facebook-twitter-g Plugin up to 4.2.7 on WordPress. The affected element is an unknown function of the file wp-admin/admin.php?page=nxssnap-reposter&action=edit. Such manipulation of the argument item leads to cross site scripting. This vulnerability is documented as CVE-2019-9911. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in social-networks-auto-poster-facebook-twitter-g Plugin up to 4.2.7 on WordPress (Social Network Software) and classified as problematic. Affected by this issue is an unknown code block of the file wp-admin/admin.php?page=nxssnap-reposter&action=edit. The manipulation of the argument item with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. CVE summarizes:
The social-networks-auto-poster-facebook-twitter-g plugin before 4.2.8 for WordPress has wp-admin/admin.php?page=nxssnap-reposter&action=edit item XSS.
The bug was discovered 10/25/2018. The weakness was released 03/22/2019 as not defined mailinglist post (Full-Disclosure). The advisory is shared for download at seclists.org. This vulnerability is handled as CVE-2019-9911 since 03/21/2019. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
The vulnerability was handled as a non-public zero-day exploit for at least 148 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 4.2.8 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: 🔍
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: social-networks-auto-poster-facebook-twitter-g Plugin 4.2.8
Timeline
10/25/2018 🔍03/21/2019 🔍
03/22/2019 🔍
03/23/2019 🔍
05/19/2020 🔍
Sources
Advisory: seclists.orgStatus: Not defined
CVE: CVE-2019-9911 (🔍)
GCVE (CVE): GCVE-0-2019-9911
GCVE (VulDB): GCVE-100-132116
Entry
Created: 03/23/2019 09:36Updated: 05/19/2020 11:17
Changes: 03/23/2019 09:36 (60), 05/19/2020 11:17 (1)
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.