dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-59557

CRITICAL · 9.3 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 ThemeMove Learts Addons learts-addons allows SQL Injection.This issue affects Learts Addons: from n/a through < 1.7.5.

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 ThemeMove Learts Addons plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. The flaw exists in versions prior to 1.7.5, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate Learts Addons to version 1.7.5 or later to remediate the SQL injection vulnerability. If patching is not immediately possible, disable the plugin until the update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Learts Addons plugin is present
    Check for the plugin directory at wp-content/plugins/learts-addons or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The Learts Addons plugin directory exists and the plugin is active
  2. Identify installed plugin version
    Open the main plugin file (learts-addons.php) or readme.txt in the plugin directory and locate the Version field in the plugin header
    Affected if Version cannot be determined or the file is not found
  3. Compare version to affected range
    Compare the installed version number to the affected range: versions prior to 1.7.5
    Affected if Installed version is 1.7.4 or lower, or any version number below 1.7.5
  4. Inspect for SQL injection indicators
    Review server error logs and database query logs for unusual SQL syntax, error messages containing SQL keywords, or suspicious query patterns targeting plugin endpoints
    Affected if Unusual SQL syntax or database errors appear in logs related to plugin functionality

The environment is affected if the Learts Addons plugin is installed and its version is prior to 1.7.5, as the SQL injection vulnerability exists in those versions.

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

Update Learts Addons to version 1.7.5 or later to remediate the SQL injection vulnerability. If patching is not immediately possible, disable the plugin until the update can be applied.

Recommended fix Moderate confidence

1.7.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes (for theme) or Plugins > Installed Plugins (for plugin)
  3. Locate the Learts Addons theme/plugin
  4. If automatic updates are enabled, the update to 1.7.5 should be available; otherwise, click 'Update Now'
  5. Alternatively, download Learts Addons version 1.7.5 or later from ThemeMove and upload via WordPress admin or FTP
  6. Verify the update was successful by checking the version number after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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