CVE-2025-54476 — joomla/filter
Fix: joomla-framework/filter@188dd3fCVE-2025-54476 is a security vulnerability in joomla/filter. A fix is available for joomla/filter — see the affected versions and patch details below.
Joomla! CMS vulnerable to XSS via the input filter
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54476.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
joomla/filter🐘joomla/filter🐘joomla/filterReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Improper handling of input could lead to a cross-site scripting (XSS) vector in the checkAttribute method of the input filter framework class.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | joomla/filter | ≥ 4.0.0&&< 4.0.1 | 4.0.1composer require joomla/filter:^4.0.1 |
| 🐘Packagist | joomla/filter | ≥ 3.0.0&&< 3.0.5 | 3.0.5composer require joomla/filter:^3.0.5 |
| 🐘Packagist | joomla/filter | all versions | 2.0.6composer require joomla/filter:^2.0.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joomla/filter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update joomla/filter to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54476 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-54476 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-54476. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-54476 in your dependencies?
O3 Security finds CVE-2025-54476 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.