dbcve.org
Joomla\!Application · Joomla

CVE-2022-23797

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to after 4.1.0 or later.
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
An issue was discovered in Joomla! 3.0.0 through 3.10.6 & 4.0.0 through 4.1.0. Inadequate filtering on the selected Ids on an request could resulted into an possible SQL injection.

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

SQL injection vulnerability in Joomla! CMS versions 3.0.0-3.10.6 and 4.0.0-4.1.0. Inadequate filtering on user-supplied 'selected Ids' parameter in requests allows attackers to inject malicious SQL code into database queries, potentially leading to data exfiltration or complete database compromise.

MitigationUpgrade to Joomla! 3.10.7 or later for the 3.x branch, or Joomla! 4.1.1 or later for the 4.x branch. Apply the security update immediately given the critical CVSS 9.8 severity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Joomla\!Application
Affected:>= 3.0.0, <= 3.10.6>= 4.0.0, <= 4.1.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine installed Joomla version
    Log into the Joomla Administrator dashboard and navigate to System > System Information > Joomla! Version, or check the libraries/cms/version/version.php file for the VERSION constant
    Affected if The installed version is between 3.0.0 and 3.10.6 inclusive, or between 4.0.0 and 4.1.0 inclusive
  2. Identify components with batch selection functionality
    Review installed Joomla extensions in Extensions > Manage > Manage. Focus on components that expose list views with batch operations such as com_banners, com_users, com_content, com_contact, or com_newsfeeds in the administrator area
    Affected if Any of these components are installed and accessible to users with permission to perform batch operations
  3. Check for unusual SQL patterns in access logs
    Review web server access logs (Apache access.log or Nginx access.log) and look for requests to administrator/index.php containing parameters like 'selected[]' or 'cid[]' with unusual characters such as quotes, UNION, or SQL keywords
    Affected if Log entries show requests with SQL injection payloads in selection parameters
  4. Verify database query logging is enabled
    Enable Joomla debug mode or database query logging via Configuration > System > Debug Settings, then review the debug logs for any suspicious queries containing injected SQL syntax
    Affected if Debug logs reveal malformed SQL queries with injected code in parameters related to item selection

You are affected if your Joomla installation version falls within 3.0.0-3.10.6 or 4.0.0-4.1.0 and you have any components with batch selection features accessible to users.

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
Upgrade available Upgrade to a release after 4.1.0
Interim mitigation

Upgrade to Joomla! 3.10.7 or later for the 3.x branch, or Joomla! 4.1.1 or later for the 4.x branch. Apply the security update immediately given the critical CVSS 9.8 severity.

Recommended fix High confidence

Joomla! 3.10.7 or Joomla! 4.1.1

  1. 1. Backup your Joomla! database and files before making any changes
  2. 2. Download Joomla! 3.10.7 (for 3.x installations) or Joomla! 4.1.1 (for 4.x installations) from the official Joomla! downloads page at https://downloads.joomla.org/
  3. 3. Extract the upgrade package to your local system
  4. 4. Upload the files to your Joomla! installation, overwriting existing files
  5. 5. Clear any Joomla! caches after the upgrade
  6. 6. Verify the site functionality and admin access
Caveat Minor point releases typically have minimal breaking changes; test in staging first

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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