Skip to content
Fencer Vulns
high 7.5

CVE-2006-2753 json

SQL injection vulnerability in MySQL 4.1.x before 4.1.20 and 5.0.x before 5.0.22 allows context-dependent attackers to execute arbitrary SQ…

published 2006-06-01 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2752

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

SQL injection vulnerability in MySQL 4.1.x before 4.1.20 and 5.0.x before 5.0.22 allows context-dependent attackers to execute arbitrary SQL commands via crafted multibyte encodings in character sets such as SJIS, BIG5, and GBK, which are not properly handled when the mysql_real_escape function is used to escape the input.

Patch / fix

  • mysql RHEL 4 4.1.20-1.RHEL4.1
  • mysql-bench RHEL 4 4.1.20-1.RHEL4.1
  • mysql-server RHEL 4 4.1.20-1.RHEL4.1

red hat advisories RHSA-2006:0544

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-2753 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux Desktop version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux ES version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux WS version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1
    fixed: vendor fix RHSA-2006:0544

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.54% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.