dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67520

HIGH · 7.6 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Tiny Solutions Media Library Tools media-library-tools allows SQL Injection.This issue affects Media Library Tools: from n/a through <= 1.6.15.

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 · moderate confidence

SQL injection vulnerability in Tiny Solutions Media Library Tools allows attackers to inject malicious SQL commands through unsanitized user input. The flaw exists in the media-library-tools component and affects versions up to and including 1.6.15. Successful exploitation could allow unauthorized data access or manipulation of the database.

MitigationUpgrade to a patched version of Media Library Tools. Until then, implement input validation and parameterization on all database queries, and apply the principle of least privilege to database accounts.

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

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
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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. Identify Media Library Tools installation
    Search the system for files or packages named 'media-library-tools' or 'Tiny Solutions Media Library Tools'. Check installed applications, plugins, or extensions in the web server's document root, CMS plugin directories, or application package managers.
    Affected if The product Tiny Solutions Media Library Tools is installed on the system
  2. Determine installed version
    Check version files, composer.json, package.json, plugin metadata, or the application's admin interface for the Media Library Tools version number. Common locations include: /wp-content/plugins/ (WordPress), /modules/, or the application's root directory.
    Affected if The installed version is 1.6.15 or lower (any version up to and including 1.6.15)
  3. Verify media-library-tools component is active
    Confirm that the media-library-tools component is loaded and enabled in the application. Check configuration files, module settings, or the application's admin panel for active components.
    Affected if The media-library-tools component is enabled and processing requests
  4. Identify user input entry points
    Review web application logs and configuration to identify endpoints or forms that accept user input and pass it to database queries through the media-library-tools component. Check for URL parameters, POST data, or API inputs.
    Affected if The application accepts user input through parameters that interact with the media-library-tools database functions

The environment is affected if Tiny Solutions Media Library Tools is installed with version 1.6.15 or lower and the media-library-tools component is actively processing user-supplied input that reaches database queries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Media Library Tools. Until then, implement input validation and parameterization on all database queries, and apply the principle of least privilege to database accounts.

Recommended fix Moderate confidence

Upgrade to Media Library Tools version 1.6.16 or latest available release

  1. Identify the current version of Media Library Tools (media-library-tools) installed in your WordPress environment
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate Media Library Tools and check the version number
  4. If version is <= 1.6.15, update to the latest available version from the WordPress plugin repository or contact the vendor for the patched release
  5. After updating, verify the plugin functions correctly and test media library operations
  6. Review WordPress audit logs to confirm no exploitation occurred prior to patching
Caveat Check plugin changelog for any breaking changes between your current version and the upgrade version before applying in production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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