flickrRSS Plugin 5.3.1 on WordPress flickrRSS.php flickrRSS_tags cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in flickrRSS Plugin 5.3.1 on WordPress. This vulnerability affects unknown code of the file flickrRSS.php. Performing a manipulation of the argument flickrRSS_tags as part of Parameter results in cross site scripting. This vulnerability was named CVE-2018-6469. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in flickrRSS Plugin 5.3.1 on WordPress (WordPress Plugin). This affects some unknown functionality of the file flickrRSS.php. The manipulation of the argument flickrRSS_tags as part of a Parameter leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
A cross-site scripting (XSS) vulnerability in flickrRSS.php in the flickrRSS plugin 5.3.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the flickrRSS_tags parameter to wp-admin/options-general.php.
The bug was discovered 02/06/2018. The weakness was presented 02/06/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2018-6469 since 01/31/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
By approaching the search of inurl:flickrRSS.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.
See VDB-112860, VDB-112861 and VDB-112862 for similar entries. Be aware that VulDB is the high quality 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.2
VulDB Base Score: 4.3
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: 🔍
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
01/31/2018 🔍02/06/2018 🔍
02/06/2018 🔍
02/06/2018 🔍
02/06/2018 🔍
01/01/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-6469 (🔍)
GCVE (CVE): GCVE-0-2018-6469
GCVE (VulDB): GCVE-100-112863
See also: 🔍
Entry
Created: 02/06/2018 18:56Updated: 01/01/2020 20:29
Changes: 02/06/2018 18:56 (59), 01/01/2020 20:29 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.