CVE-2025-7670
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-19

Last updated on: 2025-08-19

Assigner: Wordfence

Description
The JS Archive List plugin for WordPress is vulnerable to time-based SQL Injection via the build_sql_where() function in all versions up to, and including, 6.1.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-19
Last Modified
2025-08-19
Generated
2026-05-07
AI Q&A
2025-08-19
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
wordpress jquery-archive-list-widget 6.1.5
wordpress jquery-archive-list-widget 6.1.6
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in the JS Archive List WordPress plugin (up to version 6.1.5) is a time-based SQL Injection in the build_sql_where() function. It occurs because user-supplied parameters are not properly escaped or prepared in SQL queries, allowing unauthenticated attackers to append malicious SQL code to existing queries. This can be exploited to extract sensitive information from the database.


How can this vulnerability impact me? :

This vulnerability can allow an unauthenticated attacker to perform time-based SQL Injection attacks, potentially extracting sensitive information from the WordPress site's database without authorization. This could lead to data leakage, exposure of confidential information, and compromise of the site's data integrity.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability could lead to unauthorized access and extraction of sensitive personal or protected data stored in the database, which may result in non-compliance with data protection regulations such as GDPR or HIPAA. Organizations affected by this vulnerability might face legal and regulatory consequences if personal or sensitive data is exposed due to exploitation.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a time-based SQL Injection in the JS Archive List WordPress plugin versions up to 6.1.5. Detection would involve identifying if the vulnerable plugin version is installed and active on your WordPress site. Since it is a plugin vulnerability, network detection might be limited. You can check the plugin version via WordPress admin dashboard or by inspecting the plugin files. Additionally, you could attempt to detect suspicious SQL injection attempts by monitoring web server logs for unusual query parameters targeting the plugin's SQL query parameters. There are no specific commands provided in the resources for detection. A practical step is to verify the plugin version by running a command like `wp plugin list` if WP-CLI is installed, which lists installed plugins and their versions. For example: `wp plugin list | grep jquery-archive-list-widget` to check the installed version. If the version is 6.1.5 or lower, the site is vulnerable. [2, 4]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to update the JS Archive List plugin to version 6.1.6 or later, where the vulnerability has been fixed by improving SQL query preparation and using parameterized queries to prevent SQL injection. This update includes security enhancements as shown in the code improvements in version 6.1.6. If updating immediately is not possible, consider disabling the plugin temporarily to prevent exploitation. Additionally, monitor and restrict access to the affected plugin endpoints and review web server logs for suspicious activity. [3, 4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart