I/Librarian up to 4.9 Access Control ajaxdiscussion.php access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in I and Librarian up to 4.9. Affected by this issue is some unknown functionality of the file ajaxdiscussion.php of the component Access Control. Such manipulation leads to access control. This vulnerability is uniquely identified as CVE-2018-1000141. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in I and Librarian up to 4.9 and classified as critical. Affected by this issue is an unknown functionality of the file ajaxdiscussion.php of the component Access Control. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:
I, Librarian version 4.9 and earlier contains an Incorrect Access Control vulnerability in ajaxdiscussion.php that can result in any users gaining unauthorized access (read, write and delete) to project discussions.
The bug was discovered 03/23/2018. The weakness was disclosed 03/23/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2018-1000141 since 03/23/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
By approaching the search of inurl:ajaxdiscussion.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.
The entries VDB-114960, VDB-114959 and VDB-114958 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Access controlCWE: CWE-284 / CWE-266
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: 🔍
0-Day Time: 🔍
Timeline
03/23/2018 🔍03/23/2018 🔍
03/23/2018 🔍
03/23/2018 🔍
03/24/2018 🔍
12/05/2025 🔍
Sources
Advisory: 124Status: Not defined
CVE: CVE-2018-1000141 (🔍)
GCVE (CVE): GCVE-0-2018-1000141
GCVE (VulDB): GCVE-100-114962
See also: 🔍
Entry
Created: 03/24/2018 08:45Updated: 12/05/2025 22:34
Changes: 03/24/2018 08:45 (56), 01/16/2020 09:35 (1), 02/22/2023 18:28 (3), 12/05/2025 22:34 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.