| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in thorsten phpmyfaq up to 3.1.10. It has been classified as problematic. The affected element is an unknown function. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2023-0790. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in thorsten phpmyfaq up to 3.1.10 (Content Management System). CWE is classifying the issue as CWE-248. An exception is thrown from a function, but it is not caught. The impact remains unknown. The summary by CVE is:
Uncaught Exception in GitHub repository thorsten/phpmyfaq prior to 3.1.11.
The weakness was presented 02/12/2023. It is possible to read the advisory at huntr.dev. This vulnerability is uniquely identified as CVE-2023-0790 since 02/12/2023. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.1.11 eliminates this vulnerability. Applying the patch f34d84dfe551ecdd675916e45cc0606e04a0734e 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0646). Be aware that VulDB is the high quality 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.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 7.6
CNA Vector (huntr.dev): 🔍
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: Uncaught exceptionCWE: CWE-248
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 3.1.11
Patch: f34d84dfe551ecdd675916e45cc0606e04a0734e
Timeline
02/12/2023 🔍02/12/2023 🔍
02/12/2023 🔍
07/05/2025 🔍
Sources
Product: github.comAdvisory: f34d84dfe551ecdd675916e45cc0606e04a0734e
Status: Confirmed
CVE: CVE-2023-0790 (🔍)
GCVE (CVE): GCVE-0-2023-0790
GCVE (VulDB): GCVE-100-220743
EUVD: 🔍
Entry
Created: 02/12/2023 17:53Updated: 07/05/2025 16:10
Changes: 02/12/2023 17:53 (40), 03/10/2023 17:23 (1), 03/10/2023 17:31 (22), 07/05/2025 16:10 (15)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.