dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-54474

HIGH · 8.5 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 →
91/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 SQLi vulnerability in DJ-Classifieds component 3.9.2-3.10.1 for Joomla was discovered. The issue allows privileged 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 DJ-Classifieds Joomla component (versions 3.9.2-3.10.1) allows privileged users to execute arbitrary SQL commands through unsanitized input in the component's backend functionality.

MitigationUpdate to the latest patched version of DJ-Classifieds when available; in the interim, restrict privileged user access to the component and monitor database query logs for suspicious activity.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/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. Confirm DJ-Classifieds component is installed
    Log into the Joomla administrator panel, navigate to Components, and verify DJ-Classifieds appears in the list. Alternatively, check for the /components/com_djclassifieds/ directory on the filesystem.
    Affected if The component is not present in the Joomla installation.
  2. Identify the installed DJ-Classifieds version
    In the Joomla admin panel, go to Components > DJ-Classifieds. The version number is typically displayed on the main component page or in the component details. Alternatively, check the version in the manifest file at /administrator/manifests/files/dj-classifieds.xml.
    Affected if The installed version falls within 3.9.2 through 3.10.1 inclusive.
  3. Verify privileged user access exists
    In Joomla admin, navigate to Users > Manage and review user accounts. Focus on users with Super User, Administrator, or other elevated privileges that would grant access to the DJ-Classifieds component backend.
    Affected if Any privileged user accounts exist in the Joomla installation.
  4. Inspect component configuration for vulnerable parameters
    Access the DJ-Classifieds component backend and examine the URL parameters used in search, filter, or listing functions. Look for parameters that accept user input without apparent sanitization in the component code at /components/com_djclassifieds/.
    Affected if Parameters accept raw user input that could be manipulated for SQL injection.

A user is affected if DJ-Classifieds version 3.9.2 to 3.10.1 is installed AND privileged user accounts exist in the Joomla system.

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 to the latest patched version of DJ-Classifieds when available; in the interim, restrict privileged user access to the component and monitor database query logs for suspicious activity.

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-54474 — 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-54474 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