DomainMod 4.10.0 index.php new_first_name Stored cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in DomainMod 4.10.0. Impacted is an unknown function of the file /settings/profile/index.php. Performing a manipulation of the argument new_first_name as part of Parameter results in cross site scripting (Stored). This vulnerability is known as CVE-2018-11558. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in DomainMod 4.10.0. It has been classified as problematic. This affects some unknown functionality of the file /settings/profile/index.php. The manipulation of the argument new_first_name as part of a Parameter leads to a cross site scripting vulnerability (Stored). 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:
DomainMod 4.10.0 has Stored XSS in the "/settings/profile/index.php" new_first_name parameter.
The bug was discovered 05/30/2018. The weakness was published 05/30/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-11558 since 05/29/2018. It is possible to initiate the attack remotely. A authentication is required 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:settings/profile/index.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.
Similar entry is available at VDB-118366. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: StoredClass: Cross site scripting / Stored
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: 🔍
Timeline
05/29/2018 🔍05/30/2018 🔍
05/30/2018 🔍
05/30/2018 🔍
05/30/2018 🔍
03/17/2023 🔍
Sources
Product: github.comAdvisory: 66
Status: Not defined
CVE: CVE-2018-11558 (🔍)
GCVE (CVE): GCVE-0-2018-11558
GCVE (VulDB): GCVE-100-118365
See also: 🔍
Entry
Created: 05/30/2018 17:00Updated: 03/17/2023 16:52
Changes: 05/30/2018 17:00 (58), 02/09/2020 21:13 (4), 03/17/2023 16:52 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.