dbcve.org
Mysql Connector\/pythonDatabase / datastore · Oracle

CVE-2025-21548

MEDIUM · 6.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 9.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/Python). Supported versions that are affected are 9.1.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Connectors. CVSS 3.1 Base Score 6.4 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:H).

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

Vulnerability in Oracle MySQL Connector/Python affecting versions 9.1.0 and prior. Easily exploitable by high-privileged attackers with network access, requiring human interaction from a non-attacker. Successful exploitation allows unauthorized creation, deletion, or modification of critical data; unauthorized read access to subset data; and complete DoS via hang or repeatable crash.

MitigationApply Oracle's latest patch for MySQL Connector/Python to upgrade to a version beyond 9.1.0. Since human interaction is required, also review and restrict high-privileged account usage and network access paths.

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
Mysql Connector\/pythonDatabase / datastore
Affected:<= 9.1.0

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
Low
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:H

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 Connector/Python version
    Run 'pip show mysql-connector-python' or 'pip list | grep mysql-connector-python' to see the installed version
    Affected if Version is 9.1.0 or lower
  2. Verify Python environment
    Check which Python environment has the connector installed by running 'python -c "import mysql.connector; print(mysql.connector.__version__)"'
    Affected if The imported version shows 9.1.0 or prior
  3. Identify applications using the connector
    Search project dependencies for 'mysql-connector-python' in requirements.txt, setup.py, pyproject.toml, or Pipfile
    Affected if The dependency specifies version 9.1.0 or lower, or no specific version (which may resolve to an affected version)
  4. Review high-privileged account usage
    Audit application code and configuration files for database credentials belonging to high-privileged users (root, admin, or users with broad permissions)
    Affected if High-privileged database accounts are in use and accessible to the application

You are affected if MySQL Connector/Python 9.1.0 or lower is installed AND your application uses high-privileged database accounts accessible over the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 9.1.0
Interim mitigation

Apply Oracle's latest patch for MySQL Connector/Python to upgrade to a version beyond 9.1.0. Since human interaction is required, also review and restrict high-privileged account usage and network access paths.

Recommended fix Moderate confidence

mysql-connector-python > 9.1.0 (check Oracle's January 2025 CPU for exact fixed version)

  1. Check the current MySQL Connector/Python version using: pip show mysql-connector-python or pip list
  2. Consult Oracle's Critical Patch Update January 2025 for MySQL Connector/Python security fixes at oracle.com/technetwork/security-advisory/cpu-jan-2025-5217097.html
  3. Upgrade to the latest MySQL Connector/Python version that includes the fix: pip install --upgrade mysql-connector-python
  4. Verify the upgrade was successful: pip show mysql-connector-python
  5. Test application functionality to ensure the connector still works as expected
Caveat Verify application compatibility with the new connector version before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mysql Connector\/python Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21548 — 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-2025-21548 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