CVE-2006-0903

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. Limited direct impact.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2006-02-27 23:02 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 4.6 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2006-02-27 23:02 UTC

Last modified

2026-06-16 22:21 UTC

Exploit probability

1.4% · EPSS, next 30 days

Record status

Modified

Affected

• MySQL 4.1.0
• MySQL 4.1.3
• MySQL 4.1.8
• MySQL 4.1.10
• MySQL 4.1.12
• MySQL 4.1.13
• MySQL 4.1.14
• MySQL 4.1.15

Attack profile CVSS 2.0 · 4.6

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-0903.md and follow it. Check whether this project is affected by CVE-2006-0903. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge