thorsten phpmyfaq up to 3.1.11 logic error

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability was found in thorsten phpmyfaq up to 3.1.11. It has been declared as critical. The impacted element is an unknown function. Such manipulation leads to logic error. This vulnerability is documented as CVE-2023-1887. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Detailsinfo

A vulnerability, which was classified as critical, has been found in thorsten phpmyfaq up to 3.1.11 (Content Management System). Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a logic error vulnerability. Using CWE to declare the problem leads to CWE-840. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Business Logic Errors in GitHub repository thorsten/phpmyfaq prior to 3.1.12.

The weakness was released 04/06/2023. The advisory is shared for download at huntr.dev. This vulnerability is handled as CVE-2023-1887 since 04/05/2023. There are neither technical details nor an exploit publicly available.

Upgrading to version 3.1.12 eliminates this vulnerability. Applying the patch 400d9cd988d3287515c56b2ad6343026966f1a89 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-1315). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.3
NVD Vector: 🔍

CNA Base Score: 8.3
CNA Vector (huntr.dev): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Logic error
CWE: CWE-840
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: phpmyfaq 3.1.12
Patch: 400d9cd988d3287515c56b2ad6343026966f1a89

Timelineinfo

04/05/2023 🔍
04/06/2023 +1 days 🔍
04/06/2023 +0 days 🔍
07/12/2025 +828 days 🔍

Sourcesinfo

Product: github.com

Advisory: 400d9cd988d3287515c56b2ad6343026966f1a89
Status: Confirmed

CVE: CVE-2023-1887 (🔍)
GCVE (CVE): GCVE-0-2023-1887
GCVE (VulDB): GCVE-100-225056
EUVD: 🔍

Entryinfo

Created: 04/06/2023 10:08 AM
Updated: 07/12/2025 10:23 PM
Changes: 04/06/2023 10:08 AM (51), 04/23/2023 08:55 AM (1), 04/23/2023 08:56 AM (11), 07/12/2025 10:23 PM (15)
Complete: 🔍
Cache ID: 244:596:40

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!