dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10575

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 WP jQuery Pager plugin for WordPress is vulnerable to SQL Injection via the 'ids' shortcode attribute parameter handled by the WPJqueryPaged::get_gallery_page_imgs() function in all versions up to, and including, 1.4.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

SQL injection vulnerability in WP jQuery Pager plugin allows authenticated users with Contributor-level access and above to inject malicious SQL via the 'ids' shortcode attribute processed by the WPJqueryPaged::get_gallery_page_imgs() function. The vulnerability stems from insufficient escaping of user input combined with lack of prepared statements in the SQL query.

MitigationUpdate WP jQuery Pager to the latest version once available, or restrict Contributor-level user capabilities until a patch can be applied. The fix requires implementing proper $wpdb->prepare() statements for the 'ids' parameter.

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

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

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 WP jQuery Pager plugin is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-jquery-pager', 'jquery-pager', or similar. Alternatively, search the WordPress database in wp_options for plugin names containing 'jquery' and 'pager'.
    Affected if The plugin folder or database entry exists in your WordPress installation
  2. Identify the installed plugin version
    If the plugin is installed, check the main plugin file header in wp-content/plugins/<plugin-folder>/wp-jquery-pager.php (or similar) for the 'Version' field. Compare this version number to any officially listed affected versions.
    Affected if Your version matches or falls within an affected version range (if such ranges have been published by the vendor)
  3. Detect usage of the vulnerable shortcode
    Search your WordPress database (wp_posts table) or export posts/content for the shortcode pattern that includes the 'ids' attribute, such as [jquery-pager ids="..."] or similar shortcode names used by this plugin.
    Affected if Your site contains posts, pages, or custom post types that use the plugin shortcode with the 'ids' parameter
  4. Confirm shortcode processing is active
    Verify the plugin is active (not just installed) by checking the wp_options table for active_plugins, or by logging into the WordPress admin and viewing the Plugins page.
    Affected if The plugin appears in the list of active plugins and is not deactivated
  5. Review Contributor-level user accounts
    In WordPress admin under Users, check if any users have the Contributor role. Alternatively, query wp_usermeta where meta_key = 'wp_capabilities' and meta_value contains 'contributor'.
    Affected if Your WordPress site has one or more users with Contributor-level access (these users could exploit the vulnerability)

You are affected if the WP jQuery Pager plugin is installed and active, and your environment contains content using the 'ids' shortcode attribute, regardless of whether Contributor users currently exist on the site.

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 WP jQuery Pager to the latest version once available, or restrict Contributor-level user capabilities until a patch can be applied. The fix requires implementing proper $wpdb->prepare() statements for the 'ids' parameter.

Recommended fix Moderate confidence

Version greater than 1.4.0 (check WordPress plugin repository for latest stable release)

  1. 1. Identify the currently installed version of the WP jQuery Pager plugin in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the WP jQuery Pager plugin entry
  4. 4. If the installed version is 1.4.0 or lower, initiate an update to the latest available version
  5. 5. Before updating, ensure you have a recent backup of your WordPress database and files
  6. 6. After updating, verify the 'ids' shortcode attribute properly sanitizes input and the get_gallery_page_imgs() function uses prepared statements

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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