CVE-2025-7670 json
JS Archive List <= 6.1.5 - Unauthenticated SQL Injection via build_sql_where Function
published last yr. modified 4mo ago also EUVD-2025-28781
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2025-7670 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- skatox JS Archive List
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- github.com /Skatox/jquery-archive-list/commit/1c4a5749b187cc65d2c4b192b9c9890a36bf1fd2
- wordfence.com /threat-intel/vulnerabilities/id/72857d52-ac81-4eb2-93fa-7bb03265bccf?source=cve
- plugins.trac.wordpress.org /browser/jquery-archive-list-widget/tags/6.1.5/classes/class-jq-archive-list-datasource.php
- wordpress.org /plugins/jquery-archive-list-widget/#developers
- plugins.trac.wordpress.org /changeset/3341291/
Sources
- CVE List CVE-2025-7670
- NVD CVE-2025-7670
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.