How to Fix CVE-2026-21630: Joomla! CMS (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 6.9, Medium |
|---|---|
| Actively exploited? | No |
| Affected | Joomla! Project Joomla! CMS (4.0.0-5.4.3, 6.0.0-6.0.3) |
| Fixed in | Same patched build as CVE-2026-21629 |
| Type (CWE) | CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') |
CVE-2026-21630 is a sibling vulnerability in the same Joomla! Project Joomla! CMS advisory bundle as CVE-2026-21629. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-21630 matches the primary write-up.
What is different about CVE-2026-21630?
Improperly built order clauses lead to a SQL injection vulnerability in the articles webservice endpoint.
Impact is consistent with the bundle: SQL injection that can read or modify the backing database. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-21630
Apply the patched build per the primary write-up: How to Fix CVE-2026-21629.
For a quick check, confirm the running version of Joomla! CMS:
Sign in to Site Administrator > System Information and read the Joomla! Version field.
Frequently asked questions
Is CVE-2026-21630 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-21630?
CVSS rates it 6.9 (Medium). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Joomla! CMS offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-21630 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://developer.joomla.org/security-centre/1028-20260302-core-sql-injection-in-com-content-articles-webservice-endpoint.html
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-21630
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-21629
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Joomla! Project Joomla! CMS advisory bundle. Full procedure at how-to-fix-cve-2026-21629.*