CVE-2009-3480
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 · uneditedSQL injection vulnerability in the iCRM Basic (com_icrmbasic) component 1.4.2.31 for Joomla! allows remote attackers to execute arbitrary SQL commands via the p3 parameter to index.php. 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 · low confidenceSQL injection vulnerability in Joomla's iCRM Basic component (com_icrmbasic) version 1.4.2.31 allows remote attackers to execute arbitrary SQL commands via the unsanitized p3 parameter in index.php.
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= 1.4.2.31CVSS 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.
-
Verify iCRM Basic component is installedCheck for the presence of the com_icrmbasic directory in the Joomla components folder (typically /components/com_icrmbasic/ or \components\com_icrmbasic\). If using Joomla admin panel, check Components > iCRM Basic or examine the #__components database table for com_icrmbasic entry.Affected if The com_icrmbasic component directory or database entry exists on the system.
-
Confirm installed version of iCRM BasicLocate the component's main PHP file (such as com_icrmbasic/admin.icrmbasic.php, com_icrmbasic/icrmbasic.php, or a version file within the component directory) and inspect for a version number string. Alternatively, query the Joomla #__components table for the version field of the com_icrmbasic entry.Affected if The discovered version is exactly 1.4.2.31.
-
Check if component is publicly accessibleAttempt to access the component via the Joomla entry point using the URL pattern: /index.php?option=com_icrmbasic or verify that the component is published and accessible in the Joomla extension manager.Affected if The component is installed and enabled, making the vulnerable code path reachable.
-
Inspect the vulnerable parameter handlingExamine the main component PHP file (typically index.php within com_icrmbasic/) for usage of the 'p3' parameter without proper sanitization or parameterized queries. Look for direct insertion of $_REQUEST['p3'] or similar into SQL queries.Affected if The p3 parameter is used in SQL queries without sanitization or prepared statements.
The system is affected if iCRM Basic component version 1.4.2.31 is installed and the vulnerable p3 parameter handling code is present 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 dataImplement proper input validation and parameterized queries for the p3 parameter, or upgrade/patch the component if a fix is available from the vendor.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3480 — 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-2009-3480 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