dbcve.org
Joomla\!Application · Joomla

CVE-2022-23796

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to after 3.10.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.7.0 through 3.10.6. Lack of input validation could allow an XSS attack using com_fields.

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

A cross-site scripting (XSS) vulnerability exists in Joomla! versions 3.7.0 through 3.10.6 due to insufficient input validation in the com_fields component. An attacker could inject malicious scripts through field inputs that would execute in the context of other users' sessions.

MitigationUpgrade Joomla! to version 3.10.7 or later to obtain the patched input validation for the com_fields component.

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.7.0, <= 3.10.6

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Joomla version
    Access the Joomla administrator dashboard and check the version information, or inspect the file /administrator/manifests/files/joomla.xml for the <version> tag, or query the #__extensions table in the database for the joomla package entry.
    Affected if The installed version is 3.7.0 through 3.10.6 (inclusive)
  2. Confirm com_fields component is present
    Navigate to the Joomla administrator panel and look for Components > Custom Fields (com_fields), or query the #__extensions database table for entry with type='component' and element='com_fields'.
    Affected if The com_fields component is installed and enabled in the Joomla instance
  3. Identify active custom field configurations
    Query the #__fields database table for any published field definitions, or access the Custom Fields interface in the administrator panel to list any created fields.
    Affected if Any custom field definitions exist in the system (the vulnerability is triggered through field input processing)
  4. Check field input handling
    Review the com_fields component code in /components/com_fields/ to confirm the input validation routines, or test creating a new custom field with script tags in the label or name parameters.
    Affected if The com_fields component processes user-supplied input without proper validation/sanitization (versions 3.7.0-3.10.6 lack the patched validation)

The environment is affected if Joomla version is between 3.7.0 and 3.10.6 inclusive AND the com_fields component is enabled and contains custom field configurations that accept user input.

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 3.10.6
Interim mitigation

Upgrade Joomla! to version 3.10.7 or later to obtain the patched input validation for the com_fields component.

Recommended fix High confidence

Joomla! 3.10.7 or later (recommended: latest 3.x LTS release)

  1. 1. Back up your Joomla! database and filesystem before proceeding with any upgrade.
  2. 2. Download Joomla! 3.10.7 (or the latest 3.x LTS release) from the official Joomla! downloads page at https://downloads.joomla.org/
  3. 3. Extract the upgrade package to your local machine.
  4. 4. Upload the extracted files to your Joomla! root directory, overwriting existing files.
  5. 5. Navigate to the Joomla! administrator panel and complete any database migration prompts if presented.
  6. 6. Verify the upgrade was successful by checking the Joomla! version in System > System Information.
  7. 7. Test the com_fields component to ensure the XSS vulnerability has been addressed.

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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