# CVE-2025-25226: [20250401] - Joomla Framework - SQL injection vulnerability in quoteNameStr method of Database package

> SQL injection in Joomla Framework's quoteNameStr method allows attackers to manipulate database queries if custom classes use this protected method.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** BIT-joomla-2025-25226, GHSA-44v2-prcf-pc3m

## What is CVE-2025-25226?

CVE-2025-25226 is a critical SQL injection vulnerability in Joomla Joomla\!, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper handling of identifiers lead to a SQL injection vulnerability in the quoteNameStr method of the database package. Please note: the affected method is a protected method. It has no usages in the original packages in neither the 2.x nor 3.x branch and therefore the vulnerability in question can not be exploited when using the original database class. However, classes extending the affected class might be affected, if the vulnerable method is used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-25226?

5 open source packages ship an affected version, including joomla/database and joomla. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `joomla/database` | Packagist | From 1.0.0 | 2.2.0 |
| `joomla/database` | Packagist | From 1.0.0 | 2.2.0 |
| `joomla/database` | Packagist | From 3.0.0 | 3.4.0 |
| `joomla/database` | Packagist | From 3.0.0 | 3.4.0 |
| `joomla` | Bitnami | From 1.0.0 | 5.0.3 |

Products: Joomla Joomla\!.

## How do I fix CVE-2025-25226?

Upgrade joomla/database to a fixed version for your release line: 2.2.0 or 3.4.0.

## Is CVE-2025-25226 being exploited?

There is no known exploitation of CVE-2025-25226 in the wild and no public exploit code.

## Other vulnerabilities in Joomla Joomla\!

- [CVE-2016-10033](https://insights.sbomify.com/CVE-2016-10033/): PHPMailer Command Injection (critical 9.8, exploited in the wild)
- [CVE-2023-23752](https://insights.sbomify.com/CVE-2023-23752/): Joomla! Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2026-48902](https://insights.sbomify.com/CVE-2026-48902/): Joomla! Core - [20260518] - Transport encryption downgrade for password and username reset links (critical 9.8)
- [CVE-2022-23795](https://insights.sbomify.com/CVE-2022-23795/): [20220303] - Core - User row are not bound to a authentication mechanism (critical 9.8)
- [CVE-2022-23797](https://insights.sbomify.com/CVE-2022-23797/): [20220305] - Core - Inadequate filtering on the selected Ids (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25226 and fix it if it is affected.

What it is: CVE-2025-25226 is a critical SQL injection vulnerability in Joomla Joomla\!, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25226 in the wild and no public exploit code.

Affected packages and fixed versions:
- joomla/database (Packagist): affected from 1.0.0; fixed in 2.2.0
- joomla/database (Packagist): affected from 1.0.0; fixed in 2.2.0
- joomla/database (Packagist): affected from 3.0.0; fixed in 3.4.0
- joomla/database (Packagist): affected from 3.0.0; fixed in 3.4.0
- joomla (Bitnami): affected from 1.0.0; fixed in 5.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-25226/ (Markdown: https://insights.sbomify.com/CVE-2025-25226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25226
- OSV: https://osv.dev/vulnerability/CVE-2025-25226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-25226/
Summaries are generated and may contain mistakes; the official description above is the record.