Joomla! vulnerable to Cross-site Scripting

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2011-2509: 1.09% estimated exploitation activity in the next 30 days; percentile 65.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

14 May 2022, 03:08 UTC

Last modified by the source

12 Apr 2025, 01:57 UTC

Source last checked

26 Oct 2026, 14:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vcq7-x4wr-w2mj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2011-2509

Advisory: Joomla! vulnerable to Cross-site Scripting
IDs: CVE-2011-2509, GHSA-vcq7-x4wr-w2mj
Record: https://patchnext.com/advisories/cve-2011-2509 (revision 1, source checked 26 Oct 2026, 14:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: joomla/joomla-cms 1.6.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist joomla/joomla-cms: affected < 1.6.4; fixed in 1.6.4

## Suggested inspection (read-only)
- Packagist joomla/joomla-cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on joomla/joomla-cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vcq7-x4wr-w2mj (GitHub-reviewed advisory GHSA-vcq7-x4wr-w2mj lists affected ranges: Packagist joomla/joomla-cms >=0 <1.6.4)

Commands are suggestions: review each one before running it.