Skip to content

← Public intelligence

Packagist package

joomla/joomla-cms

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

8 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5PackagistPublished

    Joomla CMS Multi-Factor Authentication Bypass

    CVE-2025-25227 · GHSA-6423-85cc-8gf6

    Affected
    • Packagist joomla/joomla-cms >= 5.0.0, < 5.2.6; >= 4.0.0, < 4.4.13
    Fixed in
    4.4.135.2.6· Vendor fix available
    Issue
    Insufficient state checks lead to a vector that allows to bypass 2FA checks.

    Recommended action: Upgrade to 5.2.6 or 4.4.13 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.1PackagistPublished

    Joomla! XSS in Default Templates

    CVE-2019-16725 · GHSA-v84j-vh7x-g7j6

    Affected
    • Packagist joomla/joomla-cms >= 3.0.0, < 3.9.12
    Fixed in
    3.9.12· Vendor fix available
    Issue
    In Joomla! 3.x before 3.9.12, inadequate escaping allowed XSS attacks using the logo parameter of the default templates.

    Recommended action: Upgrade to 3.9.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Low, CVSS 1.3PackagistPublished

    Joomla! vulnerable to Cross-site Scripting

    CVE-2011-4332 · GHSA-hq9x-8m8j-5hmh

    Affected
    • Packagist joomla/joomla-cms <= 1.6.3
    Fixed in
    1.6.4· Vendor fix available
    Issue
    Multiple cross-site scripting (XSS) vulnerabilities in Joomla! 1.6.3 and earlier allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    Recommended action: Upgrade to 1.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Low, CVSS 1.3PackagistPublished

    Joomla! Cross-site Scripting vulnerability

    CVE-2013-5583 · GHSA-5xmg-w578-gq5j

    Affected
    • Packagist joomla/joomla-cms <= 3.1.5
    Fixed in
    3.1.6· Vendor fix available
    Issue
    Cross-site scripting (XSS) vulnerability in libraries/idnaconvert/example.php in Joomla! 3.1.5 allows remote attackers to inject arbitrary web script or HTML via the lang parameter.

    Recommended action: Upgrade to 3.1.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. Medium, CVSS 4.8PackagistPublished

    Joomla! XSS Vulnerability

    CVE-2018-11326 · GHSA-g3m5-vvj7-xrwv

    Affected
    • Packagist joomla/joomla-cms >= 3.0.0, < 3.8.8
    Fixed in
    3.8.8· Vendor fix available
    Issue
    An issue was discovered in Joomla! Core starting in 3.0.0 and prior to 3.8.8. Inadequate input filtering leads to a multiple XSS vulnerabilities. Additionally, the default filtering settings could potentially allow users of the default Administrator user group to perform a XSS attack.

    Recommended action: Upgrade to 3.8.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  6. UnratedPackagistPublished

    Joomla! vulnerable to Cross-site Scripting

    CVE-2010-1649 · GHSA-fj57-vhrc-73r7

    Affected
    • Packagist joomla/joomla-cms >= 1.5, <= 1.5.17
    Fixed in
    1.5.18· Vendor fix available
    Issue
    Multiple cross-site scripting (XSS) vulnerabilities in the back end in Joomla! 1.5 through 1.5.17 allow remote attackers to inject arbitrary web script or HTML via unknown vectors related to "various administrator screens," possibly the search parameter in administrator/index.php.

    Recommended action: Upgrade to 1.5.18 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  7. Medium, CVSS 5.3PackagistPublished

    Joomla! vulnerable to Cross-site Scripting

    CVE-2011-2509 · GHSA-vcq7-x4wr-w2mj

    Affected
    • Packagist joomla/joomla-cms < 1.6.4
    Fixed in
    1.6.4· Vendor fix available
    Issue
    Multiple cross-site scripting (XSS) vulnerabilities in Joomla! before 1.6.4 allow remote attackers to inject arbitrary web script or HTML via (1) the query string to the comcontact component, as demonstrated by the Itemid parameter to index.php; (2) the query string to the comcontent component, as demonstrated by the filterorder parameter to index.php; (3) the query string to the comnewsfeeds component, as demonstrated by an arbitrary parameter to index.php; or (4) the option parameter in a reset.request action to index.php; and, when Internet Explorer or Konqueror is used, (5) allow remote attackers to inject arbitrary web script or HTML via the searchword parameter in a search action to index.php in the comsearch component.

    Recommended action: Upgrade to 1.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  8. Critical, CVSS 9.8PackagistPublished

    Joomla! Object Injection Vulnerability

    CVE-2019-7743 · GHSA-5m3w-rvvh-8fx6

    Affected
    • Packagist joomla/joomla-cms >= 2.5.0, < 3.9.3
    Fixed in
    3.9.3· Vendor fix available
    Issue
    An issue was discovered in Joomla! before 3.9.3. The phar:// stream wrapper can be used for object injection attacks because there is no protection mechanism (such as the TYPO3 PHAR stream wrapper) to prevent use of the phar:// handler for non .phar-files.

    Recommended action: Upgrade to 3.9.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →