dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22350

HIGH · 7.6 CVSS v3.1 Published 2025-01-07
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 WpIndeed Ultimate Learning Pro allows SQL Injection.This issue affects Ultimate Learning Pro: from n/a through 3.9.

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 WpIndeed Ultimate Learning Pro WordPress plugin allows authenticated or unauthenticated attackers to inject malicious SQL commands through unsanitized user input in affected parameters, potentially enabling unauthorized data access, modification, or database compromise.

MitigationUpdate to the latest patched version of Ultimate Learning Pro when available; otherwise, implement prepared statements/parameterized queries or proper input sanitization for all database queries that process user-supplied data.

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. Verify Ultimate Learning Pro plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Ultimate Learning Pro' by WpIndeed in the list.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, click on the Ultimate Learning Pro plugin to view its details, or check the plugin's main PHP file header for the 'Version' comment. Alternatively, access the plugin directory via FTP or file manager and locate the primary plugin file.
    Affected if The displayed version does not match the patched version or falls within an affected version range
  3. Inspect plugin source for SQL query patterns
    Access the plugin files via file manager or FTP. Search for database query functions (such as $wpdb->prepare, $wpdb->query, or direct SQL execution) that handle user-supplied input from $_GET, $_POST, or $_REQUEST superglobals without proper sanitization.
    Affected if User input from request parameters is used directly in SQL queries without prepared statements or escaping functions
  4. Check affected input parameters
    Review plugin files that process request parameters for signs of unsanitized input being passed to database queries. Common vulnerable locations include search fields, filters, ID parameters, and sorting options.
    Affected if Parameters accepting user input are processed in SQL queries without using $wpdb->prepare() or equivalent parameterized query methods
  5. Test for SQL injection vulnerability
    If you have access to a staging environment, use a SQL injection testing tool or manually inject SQL syntax (such as a single quote ') into plugin parameters observed in HTTP requests to see if database errors are returned.
    Affected if The application returns database error messages or exhibits unexpected behavior when special SQL characters are provided in input fields

If Ultimate Learning Pro plugin is installed and user-supplied input is used in SQL queries without prepared statements or proper sanitization, the environment is likely affected by this SQL injection vulnerability.

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

Update to the latest patched version of Ultimate Learning Pro when available; otherwise, implement prepared statements/parameterized queries or proper input sanitization for all database queries that process user-supplied data.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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