LayerBB up to 1.1.3 System Settings admin/general.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in LayerBB up to 1.1.3. It has been rated as problematic. Affected is an unknown function of the file admin/general.php of the component System Settings. This manipulation causes cross-site request forgery. The identification of this vulnerability is CVE-2019-16531. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in LayerBB up to 1.1.3. It has been declared as problematic. Affected by this vulnerability is an unknown function of the file admin/general.php of the component System Settings. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:
LayerBB before 1.1.4 has multiple CSRF issues, as demonstrated by changing the System Settings via admin/general.php.
The weakness was shared 09/20/2019. This vulnerability is known as CVE-2019-16531 since 09/19/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:admin/general.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.1.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47403). 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: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: LayerBB 1.1.4
Patch: github.com
Timeline
09/19/2019 🔍09/20/2019 🔍
09/20/2019 🔍
08/27/2025 🔍
Sources
Advisory: 154549Status: Confirmed
CVE: CVE-2019-16531 (🔍)
GCVE (CVE): GCVE-0-2019-16531
GCVE (VulDB): GCVE-100-142009
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/20/2019 10:53Updated: 08/27/2025 18:51
Changes: 09/20/2019 10:53 (53), 08/31/2020 12:23 (1), 12/26/2023 14:44 (6), 12/26/2023 14:45 (1), 08/27/2025 18:51 (25)
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.