Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

GHSA-6423-85cc-8gf6 — joomla/joomla-cms

HIGH

GHSA-6423-85cc-8gf6 is a high-severity (CVSS 7.5) Improper Authentication vulnerability in joomla/joomla-cms. A fix is available for joomla/joomla-cms — see the affected versions and patch details below.

Joomla CMS Multi-Factor Authentication Bypass

Also known asBIT-joomla-2025-25227CVE-2025-25227
Published
Apr 8, 2025
Updated
Jun 5, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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 GHSA-6423-85cc-8gf6.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-6423-85cc-8gf6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐘joomla/joomla-cms🐘joomla/joomla-cms

Real-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

Insufficient state checks lead to a vector that allows to bypass 2FA checks.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistjoomla/joomla-cms≥ 5.0.0&&< 5.2.65.2.6composer require joomla/joomla-cms:^5.2.6
🐘Packagistjoomla/joomla-cms≥ 4.0.0&&< 4.4.134.4.13composer require joomla/joomla-cms:^4.4.13

Affected Products

1 product · 2 configurations
Application
joomla\!joomla
≥ 5.0.0 && < 5.2.6
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joomla/joomla-cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update joomla/joomla-cms to 5.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6423-85cc-8gf6 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Insufficient state checks lead to a vector that allows to bypass 2FA checks.
O3 Security · Impact-Aware SCA

Is GHSA-6423-85cc-8gf6 in your dependencies?

Find it across Packagist, including transitive dependencies.

GHSA-6423-85cc-8gf6: joomla/joomla-cms | O3 Security