CVE-2025-10575: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ivycat WP jQuery Pager
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.
AI Analysis
Technical Summary
CVE-2025-10575 is an SQL Injection vulnerability identified in the WP jQuery Pager plugin for WordPress, specifically in versions up to and including 1.4.0. The vulnerability stems from insufficient escaping and lack of proper preparation of the 'ids' shortcode attribute parameter within the WPJqueryPaged::get_gallery_page_imgs() function. This flaw allows authenticated users with Contributor-level permissions or higher to append arbitrary SQL queries to existing database queries. Since Contributors typically have limited privileges, this vulnerability significantly elevates the risk by enabling them to extract sensitive information from the WordPress database without requiring higher administrative rights. The attack vector is remote and does not require user interaction, but it does require authentication, which limits exposure to some extent. The vulnerability impacts confidentiality by potentially exposing sensitive data but does not affect data integrity or availability. The CVSS v3.1 score of 6.5 reflects a medium severity, considering the ease of exploitation (low complexity), the requirement for authentication, and the potential impact on confidentiality. No public exploits have been reported yet, but the vulnerability poses a significant risk to websites using this plugin, especially those with multiple contributors. The lack of a patch at the time of publication necessitates immediate mitigation steps to prevent exploitation.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized disclosure of sensitive data stored in WordPress databases, including user information, content, and possibly configuration details. Organizations relying on WordPress sites with multiple contributors are particularly vulnerable, as attackers with Contributor-level access can exploit this flaw to extract confidential information. This could lead to data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. The impact is heightened for sectors with stringent data protection requirements such as finance, healthcare, and government institutions. Additionally, compromised WordPress sites can serve as footholds for further attacks, including phishing or malware distribution. The medium severity suggests that while the threat is serious, it is not immediately critical, but timely remediation is essential to prevent escalation.
Mitigation Recommendations
1. Immediately restrict Contributor-level user permissions to only trusted individuals and review existing user roles to minimize exposure. 2. Monitor and audit Contributor activities for suspicious behavior related to shortcode usage or database queries. 3. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL Injection attempts targeting the 'ids' parameter in the WP jQuery Pager plugin. 4. Apply any available patches or updates from the plugin vendor as soon as they are released. 5. If patches are not yet available, consider temporarily disabling the WP jQuery Pager plugin or removing the vulnerable shortcode usage from WordPress content. 6. Harden WordPress installations by enforcing least privilege principles, disabling unnecessary plugins, and keeping all components up to date. 7. Conduct regular security assessments and penetration testing focusing on plugin vulnerabilities. 8. Educate content contributors about secure usage practices and the risks of plugin vulnerabilities. These steps go beyond generic advice by focusing on user role management, targeted WAF rules, and operational controls specific to this vulnerability.
Affected Countries
Germany, United Kingdom, France, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria
CVE-2025-10575: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ivycat WP jQuery Pager
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-10575 is an SQL Injection vulnerability identified in the WP jQuery Pager plugin for WordPress, specifically in versions up to and including 1.4.0. The vulnerability stems from insufficient escaping and lack of proper preparation of the 'ids' shortcode attribute parameter within the WPJqueryPaged::get_gallery_page_imgs() function. This flaw allows authenticated users with Contributor-level permissions or higher to append arbitrary SQL queries to existing database queries. Since Contributors typically have limited privileges, this vulnerability significantly elevates the risk by enabling them to extract sensitive information from the WordPress database without requiring higher administrative rights. The attack vector is remote and does not require user interaction, but it does require authentication, which limits exposure to some extent. The vulnerability impacts confidentiality by potentially exposing sensitive data but does not affect data integrity or availability. The CVSS v3.1 score of 6.5 reflects a medium severity, considering the ease of exploitation (low complexity), the requirement for authentication, and the potential impact on confidentiality. No public exploits have been reported yet, but the vulnerability poses a significant risk to websites using this plugin, especially those with multiple contributors. The lack of a patch at the time of publication necessitates immediate mitigation steps to prevent exploitation.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized disclosure of sensitive data stored in WordPress databases, including user information, content, and possibly configuration details. Organizations relying on WordPress sites with multiple contributors are particularly vulnerable, as attackers with Contributor-level access can exploit this flaw to extract confidential information. This could lead to data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. The impact is heightened for sectors with stringent data protection requirements such as finance, healthcare, and government institutions. Additionally, compromised WordPress sites can serve as footholds for further attacks, including phishing or malware distribution. The medium severity suggests that while the threat is serious, it is not immediately critical, but timely remediation is essential to prevent escalation.
Mitigation Recommendations
1. Immediately restrict Contributor-level user permissions to only trusted individuals and review existing user roles to minimize exposure. 2. Monitor and audit Contributor activities for suspicious behavior related to shortcode usage or database queries. 3. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL Injection attempts targeting the 'ids' parameter in the WP jQuery Pager plugin. 4. Apply any available patches or updates from the plugin vendor as soon as they are released. 5. If patches are not yet available, consider temporarily disabling the WP jQuery Pager plugin or removing the vulnerable shortcode usage from WordPress content. 6. Harden WordPress installations by enforcing least privilege principles, disabling unnecessary plugins, and keeping all components up to date. 7. Conduct regular security assessments and penetration testing focusing on plugin vulnerabilities. 8. Educate content contributors about secure usage practices and the risks of plugin vulnerabilities. These steps go beyond generic advice by focusing on user role management, targeted WAF rules, and operational controls specific to this vulnerability.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-16T18:39:03.867Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68ef5c7dc4f69c9730e569cf
Added to database: 10/15/2025, 8:34:05 AM
Last enriched: 10/15/2025, 8:54:46 AM
Last updated: 10/15/2025, 10:56:06 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-9967: CWE-288 Authentication Bypass Using an Alternate Path or Channel in gsayed786 Orion SMS OTP Verification
CriticalCVE-2025-11728: CWE-306 Missing Authentication for Critical Function in oceanpayment Oceanpayment CreditCard Gateway
MediumCVE-2025-11722: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in ikhodal Woocommerce Category and Products Accordion Panel
HighCVE-2025-11701: CWE-862 Missing Authorization in quicoto Zip Attachments
MediumCVE-2025-11692: CWE-862 Missing Authorization in quicoto Zip Attachments
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.