Com SalesrepApplication · Joomla
CVE-2008-0854
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 com_salesrep component for Joomla! and Mambo allows remote attackers to execute arbitrary SQL commands via the rid parameter in a showrep action to index.php.
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 com_salesrep Joomla!/Mambo component allows remote attackers to execute arbitrary SQL commands via the 'rid' parameter in a 'showrep' action to index.php. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant risk of data exposure or compromise.
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
Com SalesrepApplication
all versionsall versionsCVSS 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.
-
Identify if com_salesrep component is installedCheck the /components/com_salesrep/ directory exists on the Joomla or Mambo web server. On Joomla, also query the #__extensions table for name='com_salesrep' or inspect the /administrator/components/com_salesrep/ directory.Affected if The com_salesrep directory exists in /components/ or is registered in the extensions database table.
-
Verify the vulnerable index.php endpoint is accessibleAttempt to access the URL pattern: index.php?option=com_salesrep&task=showrep (or task=showrep&rid=1) to confirm the component handles the showrep action.Affected if The page loads without being blocked or returning a 404, indicating the component route is active.
-
Confirm the rid parameter is processed without input sanitizationInspect the PHP source file handling the showrep task, typically in /components/com_salesrep/salesrep.php or a similar controller file. Look for direct use of the 'rid' parameter in SQL queries without escaping or prepared statements.Affected if The code contains SQL queries using $_REQUEST['rid'] or $_GET['rid'] directly in the query string without escaping functions or parameterized queries.
-
Check for outbound SQL injection indicatorsReview web server access logs for unusual query patterns in the rid parameter, such as single quotes, UNION SELECT, or boolean-based payloads like ' OR '1'='1.Affected if Log analysis reveals SQL injection payloads targeting the rid parameter in requests to the com_salesrep component.
The environment is affected if the com_salesrep component is installed and the showrep action with the rid parameter is accessible, since all versions of Joomla and Mambo Com Salesrep are vulnerable to SQL injection.
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 use parameterized queries (prepared statements) for the 'rid' parameter in the showrep action to prevent SQL injection attacks.
Fix this in Com Salesrep
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-2008-0854 — 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-2008-0854 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