Joomla\!Application · Joomla
CVE-2025-25226
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the protected quoteNameStr method of a database package due to improper identifier handling. The affected method is unused in the original 2.x and 3.x branches, making the original database class non-exploitable. However, any custom class that extends the affected class and invokes this protected method could be vulnerable to SQL injection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Joomla\!Application
>= 1.0.0, < 2.2.0>= 3.0.0, < 3.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check your Joomla versionNavigate to Administrator > Help > System Info > Version Information, or check the file /libraries/cms/version.php for the $RELEASE variable valueAffected if The version is >= 1.0.0 and < 2.2.0, OR >= 3.0.0 and < 3.4.0
-
Locate custom database subclassesSearch your codebase for PHP classes that extend the Joomla database class (typically extends JDatabase or similar base database class). Look for 'extends JDatabase' or 'extends Joomla\Database' patterns in custom or third-party extension code.Affected if Any custom class found that extends the Joomla database base class
-
Inspect subclasses for quoteNameStr usageIn any identified custom database subclasses, search for any direct or indirect calls to the protected method quoteNameStr. Review the method implementation in the parent class at /libraries/joomla/database/database.php (2.x) or /libraries/src/Database/DatabaseDriver.php (3.x) to confirm it is protected.Affected if The custom subclass explicitly calls or inherits code that invokes the quoteNameStr method on user-controlled input
-
Verify input handling in vulnerable code pathsIf quoteNameStr is called, trace the input passed to it. Determine whether that input originates from user-supplied data (request parameters, user input fields, or external APIs) without prior sanitization.Affected if User-controlled data flows into quoteNameStr without being sanitized through Joomla's query builder or escape methods
You are affected only if your Joomla version falls in the affected ranges AND you have a custom class extending the database class that invokes the protected quoteNameStr method with unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.03.4.0
Audit any subclasses that extend the affected database class for usage of the quoteNameStr method. If found, either avoid using it or implement proper input sanitization before passing identifiers. Apply vendor patches when available.
Joomla 2.x: upgrade to 2.2.0 or later; Joomla 3.x: upgrade to 3.4.0 or later
- 1. Identify your current Joomla! version by checking the administration dashboard or version file
- 2. For Joomla! 2.x (versions 1.0.0 to 2.1.x): Backup your database and files before upgrading
- 3. For Joomla! 2.x: Upgrade to Joomla! 2.2.0 or later (the 2.x branch is end-of-life; consider migrating to a supported version if possible)
- 4. For Joomla! 3.x (versions 3.0.0 to 3.3.x): Backup your database and files before upgrading
- 5. For Joomla! 3.x: Upgrade to Joomla! 3.4.0 or later (note: Joomla 3.x reached end-of-life in 2023; consider migrating to Joomla 4.x or 5.x)
- 6. After upgrade, verify the site functionality and check that custom extensions extending the database class do not use the quoteNameStr method unsafely
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-25226 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data