dbcve.org
MySQLDatabase / datastore

CVE-2007-2692

MEDIUM · 6.0 CVSS v2.0 Published 2007-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The mysql_change_db function in MySQL 5.0.x before 5.0.40 and 5.1.x before 5.1.18 does not restore THD::db_access privileges when returning from SQL SECURITY INVOKER stored routines, which allows remote authenticated users to gain privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The mysql_change_db function in MySQL 5.0.x before 5.0.40 and 5.1.x before 5.1.18 fails to restore THD::db_access privileges when returning from SQL SECURITY INVOKER stored routines, allowing authenticated users to retain elevated privileges beyond their intended scope.

MitigationUpgrade MySQL server to version 5.0.40 or later for 5.0.x branches, or 5.1.18 or later for 5.1.x branches. Alternatively, avoid using SQL SECURITY INVOKER stored routines until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.5.0.21= 5.0.10= 5.0.15= 5.0.16= 5.0.17= 5.0.20
MySQLDatabase / datastore
Affected:= 5.0.0= 5.0.3= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.11= 5.0.12= 5.0.13= 5.0.14= 5.0.18= 5.0.19

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MySQL server version
    Run SELECT VERSION(); or mysqld --version from command line
    Affected if Version is 5.0.x before 5.0.40 or 5.1.x before 5.1.18 (e.g., 5.0.20, 5.1.10)
  2. Identify SQL SECURITY INVOKER stored routines
    Query the mysql.routines table: SELECT ROUTINE_NAME, ROUTINE_TYPE, SECURITY_TYPE FROM mysql.routines WHERE SECURITY_TYPE = 'INVOKER';
    Affected if Any stored procedures or functions with SECURITY_TYPE = 'INVOKER' exist in the database
  3. Verify database-level privileges configuration
    Run SHOW GRANTS FOR CURRENT_USER(); to view current user's privileges, especially at the database level
    Affected if User has limited db-level privileges but unexpectedly accesses tables in databases where they lack explicit grants
  4. Test for privilege escalation behavior
    Create a test INVOKER stored procedure that references a table in a database where the invoker lacks direct privileges, then execute it as a restricted user
    Affected if The restricted user can access tables they should not have access to after calling the INVOKER routine

You are affected if running MySQL 5.0.x before 5.0.40 or 5.1.x before 5.1.18 AND you use SQL SECURITY INVOKER stored routines that access tables in databases where the invoker lacks explicit privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MySQL server to version 5.0.40 or later for 5.0.x branches, or 5.1.18 or later for 5.1.x branches. Alternatively, avoid using SQL SECURITY INVOKER stored routines until the patch is applied.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2692 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data