Z-BlogPHP 2.0.0 Site Settings Persistent cross site scripting ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Z-BlogPHP 2.0.0. It has been rated as problematic. The impacted element is an unknown function of the component Site Settings Handler. This manipulation causes cross site scripting (Persistent). This vulnerability is tracked as CVE-2018-11208. The attack is possible to be carried out remotely. No exploit exists. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability was found in Z-BlogPHP 2.0.0. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Site Settings Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability (Persistent). 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. The summary by CVE is:
An issue was discovered in Z-BlogPHP 2.0.0. There is a persistent XSS that allows remote attackers to inject arbitrary web script or HTML into background web site settings via the "copyright information office" field. NOTE: the vendor indicates that the product was not intended to block this type of XSS by a user with the admin privilege
The weakness was disclosed 05/16/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-11208 since 05/16/2018. The exploitation appears to be difficult. The attack can be launched remotely. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-114157, VDB-114158, VDB-117318 and VDB-117818 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔍
CNA Base Score: 4.8
CNA 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: PersistentClass: Cross site scripting / Persistent
CWE: 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: no mitigation knownStatus: 🔍
Timeline
05/16/2018 🔍05/16/2018 🔍
05/16/2018 🔍
05/16/2018 🔍
06/04/2024 🔍
Sources
Advisory: 187Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2018-11208 (🔍)
GCVE (CVE): GCVE-0-2018-11208
GCVE (VulDB): GCVE-100-117817
See also: 🔍
Entry
Created: 05/16/2018 22:20Updated: 06/04/2024 21:38
Changes: 05/16/2018 22:20 (57), 02/06/2020 08:28 (1), 03/13/2023 15:01 (3), 03/13/2023 15:02 (1), 06/04/2024 21:38 (27)
Complete: 🔍
Cache ID: 216::103
Submit
Duplicate
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.