Joomla\!Application · Joomla
CVE-2010-4696
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 · uneditedMultiple SQL injection vulnerabilities in Joomla! 1.5.x before 1.5.22 allow remote attackers to execute arbitrary SQL commands via the (1) filter_order or (2) filter_order_Dir parameter in a com_contact action to index.php, a different vulnerability than CVE-2010-4166. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 Joomla! 1.5.x (before 1.5.22) allows remote attackers to execute arbitrary SQL commands via the filter_order and filter_order_Dir parameters in the com_contact component. The vulnerable parameters are used for ordering contact list results without proper sanitization.
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.5.0= 1.5.1= 1.5.2= 1.5.3= 1.5.4= 1.5.5= 1.5.6= 1.5.7= 1.5.8= 1.5.9= 1.5.10= 1.5.11CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Determine installed Joomla versionAccess the Joomla administrator backend and navigate to Help > System Info > System Information, or inspect the /includes/version.php file for the $RELEASE variable showing the 1.5.x version numberAffected if The version is 1.5.0 through 1.5.11 (versions prior to 1.5.22)
-
Confirm com_contact component is enabledIn the Joomla administrator panel, go to Extensions > Module Manager and check for any published modules related to com_contact, or inspect the #__modules table in the database for published contact modulesAffected if The com_contact component or its related contact modules are enabled and accessible
-
Identify the contact list functionalityNavigate to the front-end of the site and access any page that displays a list of contacts, typically at index.php?option=com_contact or through a menu link to the contact componentAffected if The contact list view is accessible without authentication (the SQL injection is exploitable without login)
-
Check for the vulnerable parameters in useInspect the HTTP requests when loading the contact list page and look for filter_order and filter_order_Dir parameters in the URL or form submissionsAffected if The filter_order and filter_order_Dir parameters are present and used for ordering results without proper sanitization
You are affected if your Joomla installation is version 1.5.0 through 1.5.11 and the com_contact component is enabled and accessible, as the SQL injection vulnerability exists in the ordering parameters of the contact list functionality.
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 dataUpgrade to Joomla! 1.5.22 or later. Note that Joomla 1.5.x is end-of-life; consider migrating to a supported Joomla version (2.5.x/3.x) for long-term security.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4696 — 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-2010-4696 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