thorsten phpmyfaq up to 3.1.11 special elements into a different plane (special element injection)
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in thorsten phpmyfaq up to 3.1.11 and classified as problematic. This issue affects some unknown processing. The manipulation leads to failure to sanitize special elements into a different plane (special element injection). This vulnerability is listed as CVE-2023-1758. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in thorsten phpmyfaq up to 3.1.11 (Content Management System). It has been rated as problematic. This issue affects an unknown part. The manipulation with an unknown input leads to a failure to sanitize special elements into a different plane (special element injection) vulnerability. Using CWE to declare the problem leads to CWE-75. The product does not adequately filter user-controlled input for special elements with control implications. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository thorsten/phpmyfaq prior to 3.1.12.
The weakness was presented 04/06/2023. The advisory is shared at huntr.dev. The identification of this vulnerability is CVE-2023-1758 since 03/31/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 3.1.12 eliminates this vulnerability. Applying the patch f3380f46c464d1bc6f3ded29213c79be0de8fc57 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-1175). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 8.9
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: Failure to sanitize special elements into a different plane (special element injection)CWE: CWE-75 / CWE-707 / CWE-20
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.12
Patch: f3380f46c464d1bc6f3ded29213c79be0de8fc57
Timeline
03/31/2023 🔍04/06/2023 🔍
04/06/2023 🔍
07/06/2025 🔍
Sources
Product: github.comAdvisory: f3380f46c464d1bc6f3ded29213c79be0de8fc57
Status: Confirmed
CVE: CVE-2023-1758 (🔍)
GCVE (CVE): GCVE-0-2023-1758
GCVE (VulDB): GCVE-100-225053
EUVD: 🔍
Entry
Created: 04/06/2023 10:07Updated: 07/06/2025 20:15
Changes: 04/06/2023 10:07 (51), 04/23/2023 08:42 (1), 04/23/2023 08:44 (11), 07/06/2025 20:15 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.