dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-54475

HIGH · 8.7 CVSS v4.0 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable 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
A SQL injection vulnerability in the JS Jobs plugin versions 1.3.2-1.4.4 for Joomla allows low-privilege users to execute arbitrary SQL commands.

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

SQL injection vulnerability in the JS Jobs Joomla plugin allows authenticated low-privilege users to inject arbitrary SQL commands through unsanitized input parameters. The vulnerability affects versions 1.3.2 through 1.4.4 and could enable attackers to read, modify, or delete database contents including user credentials and sensitive application data.

MitigationUpdate JS Jobs plugin to version newer than 1.4.4 or apply vendor-supplied security patch; implement input validation and parameterized queries as interim measures if patching is delayed.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify JS Jobs plugin installation
    Check your Joomla extensions directory, administrative panel under Components or Extensions > Manage, or inspect the file system for the JS Jobs component folder (typically /components/com_jsjobs/)
    Affected if JS Jobs component is found installed on the Joomla system
  2. Locate installed version number
    Open the plugin or component manifest XML file, check the about page in the Joomla admin panel, or inspect the version defined in the main PHP file of the JS Jobs plugin
    Affected if A version number is returned that can be compared to the affected range
  3. Compare version to vulnerable range
    Compare your installed version against the affected range: 1.3.2 through 1.4.4 (inclusive)
    Affected if Installed version is 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9, 1.4.0, 1.4.1, 1.4.2, 1.4.3, or 1.4.4
  4. Confirm plugin is enabled
    Log into Joomla administrator panel, navigate to Extensions > Plugins, search for JS Jobs related plugins, and verify their status is set to Enabled
    Affected if Any JS Jobs plugin component is published and enabled

Your environment is affected if JS Jobs plugin version 1.3.2 through 1.4.4 is installed and enabled, allowing authenticated low-privilege users to access the vulnerable input parameters.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JS Jobs plugin to version newer than 1.4.4 or apply vendor-supplied security patch; implement input validation and parameterized queries as interim measures if patching is delayed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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