Com FacileformsApplication · Joomla
CVE-2008-0855
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 Facile Forms (com_facileforms) component for Joomla! and Mambo allows remote attackers to execute arbitrary SQL commands via the catid parameter 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 Facile Forms (com_facileforms) component for Joomla! and Mambo allows remote attackers to execute arbitrary SQL commands via unsanitized catid parameter passed to 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
Com FacileformsApplication
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 Facile Forms installationCheck for the com_facileforms component directory in the Joomla /components/ folder or Mambo /components/ folder. Look for /components/com_facileforms/ directory existence.Affected if The com_facileforms directory exists in the components folder, indicating Facile Forms is installed.
-
Verify component is enabledCheck the Joomla/Mambo database #__extensions table (or #__components for older versions) for the Facile Forms component entry with enabled=1 or published=1 status.Affected if The component is enabled/published in the CMS, making it accessible via the web.
-
Confirm component is publicly accessibleAttempt to access the component via URL: index.php?option=com_facileforms. A successful page load indicates the component is publicly accessible.Affected if The component loads without authentication requirements, exposing the vulnerable code path.
-
Inspect catid parameter handlingExamine the main script in /components/com_facileforms/facileforms.php or index.php for how the catid parameter is processed. Search for direct use of $_REQUEST['catid'] or $_GET['catid'] in SQL queries without sanitization functions.Affected if The catid parameter is used directly in SQL queries without escaping, filtering, or parameterized queries.
-
Check for SQL injection vulnerabilityTest the URL parameter by submitting a benign test value versus a SQL injection payload (e.g., catid=1' OR '1'='1) and observe database error messages or unexpected behavior in the response.Affected if The application returns SQL error messages or exhibits different behavior when SQL injection syntax is submitted, indicating unsanitized input is executed.
If the Facile Forms component is installed, enabled, and publicly accessible with the catid parameter being used directly in SQL queries without sanitization, the environment is affected by CVE-2008-0855.
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 catid parameter to prevent SQL injection attacks.
Fix this in Com Facileforms
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0855 — 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-0855 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