dbcve.org
Joomla\!Application · Joomla

CVE-2022-23798

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to after 4.1.0 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! 2.5.0 through 3.10.6 & 4.0.0 through 4.1.0. Inadequate validation of URLs could result into an invalid check whether an redirect URL is internal or not.

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

Joomla CMS versions 2.5.0 through 3.10.6 and 4.0.0 through 4.1.0 contain inadequate URL validation in their redirect functionality. The validation mechanism fails to properly determine whether a redirect URL is internal or external, potentially allowing attackers to craft URLs that bypass intended security restrictions on redirects.

MitigationUpgrade Joomla to version 3.10.7 or 4.1.1 or later to obtain the patched URL validation logic that properly validates whether redirect URLs are internal or external.

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:>= 2.5.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
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. Identify installed Joomla version
    Access the Joomla administrator panel and navigate to Help > System Information, or locate the version.php file in the /libraries/src/Version.php path (for Joomla 4.x) or /libraries/cms/version.php (for Joomla 3.x). The version number is displayed at the top of the System Information page.
    Affected if The version falls within 2.5.0 to 3.10.6, or 4.0.0 to 4.1.0 inclusive.
  2. Verify redirect component is active
    In the Joomla administrator panel, go to Components > Redirect. If the component appears in the menu and is accessible, it is enabled.
    Affected if The redirect component is published and accessible in the backend.
  3. Confirm redirect links functionality
    Navigate to Components > Redirect and verify that the link management interface loads. Check if the "Enabled" parameter is set to "Yes" in the component options.
    Affected if The redirect component is enabled and functional.
  4. Check URL validation behavior
    Create a test redirect using the redirect component with an external URL (such as https://example.com). Attempt to save the redirect and observe if any warning appears about the URL being external.
    Affected if No warning or validation error appears when saving an external URL as a redirect target.

The environment is affected if Joomla is installed at version 2.5.0 through 3.10.6 or 4.0.0 through 4.1.0 AND the redirect component (com_redirect) is enabled and functional.

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 Joomla to version 3.10.7 or 4.1.1 or later to obtain the patched URL validation logic that properly validates whether redirect URLs are internal or external.

Recommended fix High confidence

Joomla 3.10.7 or Joomla 4.1.1 (whichever branch is applicable)

  1. 1. Back up your current Joomla installation and database before attempting any upgrade
  2. 2. For Joomla 3.x: Navigate to Components > Joomla Update in the admin dashboard and update to version 3.10.7 or later
  3. 3. For Joomla 4.x: Navigate to System > Update > Joomla and update to version 4.1.1 or later
  4. 4. Alternatively, download the appropriate update package from downloads.joomla.org and install via Extensions > Manage > Install
  5. 5. After upgrading, verify the redirect functionality works correctly by testing legitimate internal redirects
  6. 6. Clear any Joomla caches (System > Clear Cache) after the upgrade
Caveat Minor point releases typically have minimal breaking changes; test in staging if concerned

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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