| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in thorsten phpmyfaq up to 3.1.10. It has been declared as critical. The impacted element is an unknown function. Executing a manipulation can lead to code injection. The identification of this vulnerability is CVE-2023-0792. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in thorsten phpmyfaq up to 3.1.10 (Content Management System). This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Code Injection in GitHub repository thorsten/phpmyfaq prior to 3.1.11.
The weakness was shared 02/12/2023. The advisory is shared for download at huntr.dev. This vulnerability was named CVE-2023-0792 since 02/12/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.
Upgrading to version 3.1.11 eliminates this vulnerability. Applying the patch d8964568d69488de02f0a0a58acc822eeb5c3cb1 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-0811). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 6.5
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
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: d8964568d69488de02f0a0a58acc822eeb5c3cb1
Timeline
02/12/2023 🔍02/12/2023 🔍
02/12/2023 🔍
07/05/2025 🔍
Sources
Product: github.comAdvisory: d8964568d69488de02f0a0a58acc822eeb5c3cb1
Status: Confirmed
CVE: CVE-2023-0792 (🔍)
GCVE (CVE): GCVE-0-2023-0792
GCVE (VulDB): GCVE-100-220744
EUVD: 🔍
Entry
Created: 02/12/2023 17:53Updated: 07/05/2025 21:26
Changes: 02/12/2023 17:53 (42), 03/10/2023 17:39 (1), 03/10/2023 17:46 (21), 07/05/2025 21:26 (16)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.