GNUBOARD5 up to 5.3.1.x Homepage Title config_form_update.php cf_title cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in GNUBOARD5 up to 5.3.1.x and classified as problematic. The affected element is an unknown function of the file adm/config_form_update.php of the component Homepage Title Handler. This manipulation of the argument cf_title as part of Parameter causes cross site scripting. This vulnerability appears as CVE-2018-18668. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability has been found in GNUBOARD5 up to 5.3.1.x (Forum Software) and classified as problematic. Affected by this vulnerability is an unknown part of the file adm/config_form_update.php of the component Homepage Title Handler. The manipulation of the argument cf_title as part of a Parameter leads to a cross site scripting vulnerability. 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:
GNUBOARD5 before 5.3.2.0 has XSS that allows remote attackers to inject arbitrary web script or HTML via the "homepage title" parameter, aka the adm/config_form_update.php cf_title parameter.
The weakness was presented 08/26/2019 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2018-18668 since 10/26/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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:adm/config_form_update.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.3.2.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
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
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: GNUBOARD5 5.3.2.0
Patch: github.com
Timeline
10/26/2018 🔍08/26/2019 🔍
08/27/2019 🔍
09/19/2024 🔍
Sources
Advisory: a45241f4bc46aee1ab2cc0749f6444b043681edfStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-18668 (🔍)
GCVE (CVE): GCVE-0-2018-18668
GCVE (VulDB): GCVE-100-140773
Entry
Created: 08/27/2019 06:27Updated: 09/19/2024 14:19
Changes: 08/27/2019 06:27 (59), 08/06/2020 08:13 (1), 12/04/2023 07:54 (6), 09/19/2024 14:19 (27)
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.