dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-54726

CRITICAL · 9.3 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Miguel Useche JS Archive List jquery-archive-list-widget allows SQL Injection.This issue affects JS Archive List: from n/a through < 6.1.6.

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 · moderate confidence

A SQL injection vulnerability exists in the JS Archive List (jquery-archive-list-widget) plugin in versions before 6.1.6. The vulnerability allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling unauthorized data access, modification, or deletion of database contents.

MitigationUpgrade to version 6.1.6 or later which contains the security fix. If immediate patching is not possible, disable the plugin until patched.

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

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

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. Locate the plugin installation
    Check your WordPress or CMS plugin directory for the jquery-archive-list-widget plugin folder (typically at wp-content/plugins/jquery-archive-list-widget or similar path depending on your CMS)
    Affected if The plugin folder exists in your installation
  2. Identify installed version
    Open the main plugin PHP file (usually jquery-archive-list-widget.php) and locate the version comment or header definition (look for 'Version:' or 'Version' in the plugin metadata)
    Affected if The version number displayed is less than 6.1.6 (for example, 6.1.5, 6.1.4, etc.)
  3. Confirm plugin is active
    Check your CMS admin panel plugin status or inspect your site's active plugin configuration to verify the plugin is enabled
    Affected if The plugin is currently active on your site

Your environment is affected if the jquery-archive-list-widget plugin is installed, active, and running a version numbered lower than 6.1.6

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

Upgrade to version 6.1.6 or later which contains the security fix. If immediate patching is not possible, disable the plugin until patched.

Recommended fix High confidence

6.1.6

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find the 'JS Archive List' (jquery-archive-list-widget) plugin
  4. 4. If an update is available, click 'Update Now' to update to version 6.1.6
  5. 5. Alternatively, navigate to Dashboard > Updates and select the plugin for update
  6. 6. After updating, verify the plugin version shows 6.1.6 or higher
  7. 7. Test the affected functionality to confirm the SQL injection vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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