| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in thorsten phpMyFAQ up to 3.x. Affected by this issue is some unknown functionality. Such manipulation leads to information exposure. This vulnerability is documented as CVE-2024-54141. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in thorsten phpMyFAQ up to 3.x. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a information exposure vulnerability. Using CWE to declare the problem leads to CWE-209. The product generates an error message that includes sensitive information about its environment, users, or associated data. Impacted is confidentiality. CVE summarizes:
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Prior to 4.0.0, phpMyFAQ exposes the database (ie postgreSQL) server's credential when connection to DB fails. This vulnerability is fixed in 4.0.0.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-54141 since 11/29/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 4.0.0 eliminates this vulnerability. Applying the patch b9289a0b2233df864361c131cd177b6715fbb0fe is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 8.6
CNA Vector (GitHub_M): 🔍
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: 🔍
Exploiting
Class: Information exposureCWE: CWE-209 / CWE-200 / CWE-284
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyFAQ 4.0.0
Patch: b9289a0b2233df864361c131cd177b6715fbb0fe
Timeline
11/29/2024 🔍12/06/2024 🔍
12/06/2024 🔍
08/16/2025 🔍
Sources
Product: github.comAdvisory: GHSA-vrjr-p3xp-xx2x
Status: Confirmed
CVE: CVE-2024-54141 (🔍)
GCVE (CVE): GCVE-0-2024-54141
GCVE (VulDB): GCVE-100-287156
Entry
Created: 12/06/2024 16:27Updated: 08/16/2025 00:09
Changes: 12/06/2024 16:27 (66), 08/16/2025 00:09 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.