CVE-2006-0903

Description

MySQL 5.0.18 and earlier allows local users to bypass logging mechanisms via SQL queries that contain the NULL character, which are not properly handled by the mysql_real_query function. NOTE: this issue was originally reported for the mysql_query function, but the vendor states that since mysql_query expects a null character, this is not an issue for mysql_query.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
1.374%
chance of exploitation in the next 30 days
higher than 72.5% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0
Exploit-DB: 1

Timeline

  1. 2006-02-27Published by the CNA23:00 UTC
  2. 2006-02-27First Exploit-DB entry (EDB-ID 27326)same day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

Exploit-DBTypePlatformPublishedEDB-verified
EDB-ID 27326remotelinux2006-02-27yes

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
mysql mysql4.1.0no fix listed4.1.10no fix listed4.1.12no fix listed4.1.13no fix listed4.1.14no fix listed(+11 more)not listednot listednot listednot listednot listed
oracle mysql3.23no fix listed3.23.0no fix listed3.23.1no fix listed3.23.10no fix listed3.23.11no fix listed(+108 more)not listednot listednot listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

25 references in total; the first 20 are shown.

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources