Z-BlogPHP 1.5.2 zb_system/cmd.php ZC_BLOG_NAME Stored cross site scripting ⚔ [Disputed]
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.9 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, was found in Z-BlogPHP 1.5.2. Affected is an unknown code block of the file zb_system/cmd.php. The manipulation of the argument ZC_BLOG_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. CVE summarizes:
** DISPUTED ** Z-BlogPHP 1.5.2 has a stored Cross Site Scripting Vulnerability exploitable by an administrator who navigates to "Web site settings --> Basic setting --> Website title" and enters an XSS payload via the zb_system/cmd.php ZC_BLOG_NAME parameter. NOTE: the vendor disputes the security relevance, noting it is "just a functional bug."
The weakness was presented 05/02/2018 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2018-10680 since 05/02/2018. It is possible to launch the attack remotely. The requirement for exploitation is a authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The real existence of this vulnerability is still doubted at the moment. By approaching the search of inurl:zb_system/cmd.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-114157, VDB-114158, VDB-117817 and VDB-117818 for similar entries.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CNA Base Score: 6.1
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: StoredClass: Cross site scripting / Stored
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
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/02/2018 🔍05/02/2018 🔍
05/02/2018 🔍
05/03/2018 🔍
08/05/2024 🔍
Sources
Advisory: 205Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2018-10680 (🔍)
See also: 🔍
Entry
Created: 05/03/2018 10:33 AMUpdated: 08/05/2024 10:20 AM
Changes: 05/03/2018 10:33 AM (59), 02/02/2020 08:59 AM (1), 03/08/2023 02:43 PM (3), 08/05/2024 10:20 AM (26)
Complete: 🔍
Cache ID: 18:695:40
Submit
Duplicate
No comments yet. Languages: en.
Please log in to comment.