Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-7670: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in skatox JS Archive List

0
High
VulnerabilityCVE-2025-7670cvecve-2025-7670cwe-89
Published: Tue Aug 19 2025 (08/19/2025, 07:26:27 UTC)
Source: CVE Database V5
Vendor/Project: skatox
Product: JS Archive List

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 16:27:12 UTC

Technical Analysis

CVE-2025-7670 is a critical SQL Injection vulnerability identified in the skatox JS Archive List plugin for WordPress, affecting all versions up to and including 6.1.5. The root cause is insufficient escaping and lack of proper preparation of SQL queries in the build_sql_where() function, which processes user-supplied parameters. This improper neutralization of special elements allows unauthenticated attackers to inject arbitrary SQL code into existing queries, specifically through time-based SQL Injection techniques. Time-based SQL Injection exploits the database's response time to infer data, enabling attackers to extract sensitive information such as user credentials, configuration data, or other confidential records stored in the database. The vulnerability does not require any authentication or user interaction, increasing its risk profile. The CVSS v3.1 score is 7.5, reflecting high severity due to network attack vector, low attack complexity, no privileges required, and no user interaction needed. Although no public exploits have been reported yet, the widespread use of WordPress and the plugin's presence on many sites make this a significant threat. The lack of official patches at the time of publication necessitates immediate attention from site administrators to mitigate risk.

Potential Impact

The vulnerability allows attackers to perform unauthorized data extraction from the backend database of affected WordPress sites, potentially exposing sensitive user information, site configuration details, and other confidential data. This breach of confidentiality can lead to further attacks such as identity theft, credential stuffing, or targeted phishing campaigns. Since the vulnerability does not affect data integrity or availability directly, attackers cannot modify or delete data or cause denial of service through this flaw alone. However, the exposure of sensitive data can severely damage organizational reputation, lead to regulatory non-compliance, and cause financial losses. Given the plugin’s integration with WordPress, a platform powering a significant portion of the web, the scope of affected systems is broad. The ease of exploitation without authentication or user interaction increases the likelihood of automated scanning and exploitation attempts, especially once proof-of-concept exploits become available.

Mitigation Recommendations

1. Immediate mitigation involves disabling or uninstalling the skatox JS Archive List plugin until a vendor patch is released. 2. Monitor official vendor channels and WordPress plugin repositories for updates or patches addressing CVE-2025-7670 and apply them promptly. 3. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection patterns targeting the vulnerable plugin’s endpoints. 4. Conduct thorough input validation and sanitization on all user-supplied parameters, especially those used in SQL queries, ensuring the use of parameterized queries or prepared statements. 5. Regularly audit and monitor database logs for unusual query patterns indicative of time-based SQL Injection attempts. 6. Employ least privilege principles for database accounts used by WordPress to limit data exposure in case of exploitation. 7. Educate site administrators on the risks of using outdated plugins and the importance of timely updates and security best practices.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-14T22:10:34.837Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68a4289bad5a09ad00f3caee

Added to database: 8/19/2025, 7:32:43 AM

Last enriched: 2/26/2026, 4:27:12 PM

Last updated: 3/25/2026, 4:35:52 AM

Views: 202

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses