Mike Helton aoblogger 2.3 Login login.php Username 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 has been found in Mike Helton aoblogger 2.3 and classified as critical. This issue affects some unknown processing of the file login.php of the component Login. Performing a manipulation of the argument Username results in sql injection. This vulnerability is known as CVE-2006-0311. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in Mike Helton aoblogger 2.3 (Log Management Software). This affects an unknown part of the file login.php of the component Login. The manipulation of the argument username 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. The summary by CVE is:

SQL injection vulnerability in login.php in aoblogger 2.3 allows remote attackers to execute arbitrary SQL commands via the username parameter.

The weakness was published 01/16/2006 by Aliaksandr Hartsuyeu (Website). It is possible to read the advisory at vupen.com. This vulnerability is uniquely identified as CVE-2006-0311 since 01/19/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

After even before and not, there has been an exploit disclosed. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:login.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (24142), Exploit-DB (27105), SecurityFocus (BID 16286†), OSVDB (22527†) and Secunia (SA16889†). Similar entries are available at VDB-28396 and VDB-28394. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/16/2006 🔍
01/16/2006 +0 days 🔍
01/17/2006 +0 days 🔍
01/18/2006 +1 days 🔍
01/18/2006 +0 days 🔍
01/18/2006 +0 days 🔍
01/19/2006 +0 days 🔍
03/12/2015 +3339 days 🔍
07/03/2025 +3766 days 🔍

Sourcesinfo

Advisory: vupen.com⛔
Researcher: Aliaksandr Hartsuyeu
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-0311 (🔍)
GCVE (CVE): GCVE-0-2006-0311
GCVE (VulDB): GCVE-100-28395
X-Force: 24142 - aoblogger login.php SQL injection
SecurityFocus: 16286 - AOblogger Multiple Input Validation Vulnerabilities
Secunia: 16889 - aoblogger Multiple Vulnerabilities, Moderately Critical
OSVDB: 22527 - aoblogger login.php username Field SQL Injection
Vupen: ADV-2006-0240

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/12/2015 11:11
Updated: 07/03/2025 19:03
Changes: 03/12/2015 11:11 (68), 07/17/2018 10:25 (1), 07/03/2025 19:03 (23)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

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!