CVE-2025-26854
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 · uneditedA SQL injection in Articles Good Search extension 1.0.0 - 1.2.4.0011 for Joomla allows attackers to execute arbitrary SQL commands.
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 · high confidenceSQL injection vulnerability in the Articles Good Search Joomla extension (versions 1.0.0-1.2.4.0011) allows unauthenticated attackers to execute arbitrary SQL commands via unsanitized user input in the search functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Confirm Articles Good Search extension is installedLog into the Joomla administrator panel and navigate to Extensions > Manage > Manage. Search for 'Articles Good Search' or check the installed components list. Alternatively, query the Joomla database: SELECT * FROM #__extensions WHERE name LIKE '%Articles Good Search%' OR element LIKE '%com_articles_good_search%';Affected if The extension appears in the list of installed extensions
-
Identify the installed version of the extensionIn Joomla admin, click on the Articles Good Search extension to view its details, which typically display the version number. Alternatively, query the database: SELECT version_id FROM #__extensions WHERE element LIKE '%articles_good_search%';Affected if The displayed version falls within 1.0.0 to 1.2.4.0011 (inclusive)
-
Verify the search functionality is enabled and accessibleCheck if the extension's search component is published and accessible on the frontend. In Joomla admin, navigate to Components > Articles Good Search and verify the component is enabled. Also check the menu items to confirm a search view is published.Affected if The search functionality is enabled and publicly accessible without authentication
-
Confirm the vulnerable search parameter is in useReview the front-facing search page for the extension (typically at /index.php?option=com_articles_good_search or similar). Test whether user input in the search field is submitted to the server without visible sanitization in the URL or form action.Affected if The search form accepts user input and submits it to the server, indicating the vulnerable code path is active
A user is affected if the Articles Good Search extension is installed with a version between 1.0.0 and 1.2.4.0011 and the search functionality is enabled and accessible.
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.
From vendor dataUpdate to the patched version of the extension immediately; if unavailable, disable the extension until a fix is released. Alternatively, implement proper input validation and parameterized queries in the affected code paths.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26854 — 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-26854 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