flatCore-CMS 1.4.6 user_management.php $_SERVER['PHP_SELF'] Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in flatCore-CMS 1.4.6. This affects an unknown function of the file user_management.php. Performing a manipulation of the argument $_SERVER['PHP_SELF'] as part of User-Agent results in cross site scripting (Reflected). This vulnerability is reported as CVE-2017-1000428. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in flatCore-CMS 1.4.6 (Content Management System). This affects some unknown processing of the file user_management.php. The manipulation of the argument $_SERVER['PHP_SELF'] as part of a User-Agent leads to a cross site scripting vulnerability (Reflected). 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:
flatCore-CMS 1.4.6 is vulnerable to reflected XSS in user_management.php due to the use of $_SERVER['PHP_SELF'] to build links and a stored XSS in the admin log panel by specifying a malformed User-Agent string.
The bug was discovered 01/09/2018. The weakness was disclosed 01/10/2018 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-1000428 since 01/09/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 are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:user_management.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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.0
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
Name: ReflectedClass: Cross site scripting / Reflected
CWE: 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/09/2018 🔍01/09/2018 🔍
01/09/2018 🔍
01/10/2018 🔍
01/10/2018 🔍
01/20/2023 🔍
Sources
Advisory: 35Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1000428 (🔍)
GCVE (CVE): GCVE-0-2017-1000428
GCVE (VulDB): GCVE-100-111537
Entry
Created: 01/10/2018 14:11Updated: 01/20/2023 13:12
Changes: 01/10/2018 14:11 (58), 12/20/2019 17:37 (2), 01/20/2023 13:12 (4)
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.