phpMyFAQ 1.6.7 sql injection

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.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in phpMyFAQ 1.6.7. This affects an unknown function. The manipulation results in sql injection. This vulnerability was named CVE-2006-6913. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in phpMyFAQ 1.6.7 (Content Management System). Affected is some unknown functionality. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Unspecified vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to upload arbitrary PHP scripts via unspecified vectors.

The bug was discovered 12/15/2006. The weakness was presented 12/31/2006 by Stefan Esser (Website). The advisory is available at vupen.com. This vulnerability is traded as CVE-2006-6913 since 01/09/2007. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 24001 (phpMyFAQ < 1.6.8 Multiple SQL Injection Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (31370), Tenable (24001), SecurityFocus (BID 21945†), OSVDB (32602†) and Secunia (SA23651†). See VDB-34217 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 24001
Nessus Name: phpMyFAQ < 1.6.8 Multiple SQL Injection Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/15/2006 🔍
12/15/2006 +0 days 🔍
12/31/2006 +16 days 🔍
12/31/2006 +0 days 🔍
01/08/2007 +8 days 🔍
01/08/2007 +0 days 🔍
01/09/2007 +1 days 🔍
01/10/2007 +1 days 🔍
01/14/2007 +4 days 🔍
03/12/2015 +2979 days 🔍
07/13/2019 +1584 days 🔍

Sourcesinfo

Advisory: vupen.com⛔
Researcher: Stefan Esser
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-6913 (🔍)
GCVE (CVE): GCVE-0-2006-6913
GCVE (VulDB): GCVE-100-34218
X-Force: 31370
SecurityFocus: 21945 - phpMyFAQ Unspecified Security Bypass Vulnerability
Secunia: 23651 - phpMyFAQ SQL Injection and File Upload Vulnerability, Highly Critical
OSVDB: 32602 - phpMyFAQ - Unspecified Security Bypass Issue
Vulnerability Center: 14024 - phpMyFAQ 1.6.7 and earlier Remote PHP Scripts Upload via Unspecified Vectors, High
Vupen: ADV-2007-0077

See also: 🔍

Entryinfo

Created: 03/12/2015 22:21
Updated: 07/13/2019 16:54
Changes: 03/12/2015 22:21 (67), 07/13/2019 16:54 (9)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!