CVE-2008-3737
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 · uneditedUnspecified vulnerability in (1) System Consultants La!Cooda WIZ 1.4.0 and earlier and (2) SpaceTag LacoodaST 2.1.3 and earlier allows remote attackers to execute arbitrary PHP scripts, and delete files, read files, and possibly have unknown other impact.
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 · moderate confidenceCritical unspecified vulnerability in La!Cooda WIZ and LacoodaST PHP web applications allows remote attackers to execute arbitrary PHP code (RCE), delete arbitrary files, and read arbitrary files on the server.
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<= 2.1.3<= 1.4.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 installed La!Cooda or LacoodaST PHP applicationsSearch the web server document root for directories or files containing 'lacooda' or 'lacoodast' in the name, or look for PHP files that reference 'La Cooda' or 'lacooda' in their contentAffected if The application directory or files are present on the server
-
Determine the installed version of La Cooda WizLook for a version file, readme, or index PHP file that contains a version number such as '1.4.0' or lowerAffected if The version displayed is 1.4.0 or lower
-
Determine the installed version of LacoodastLook for a version file, readme, or index PHP file that contains a version number such as '2.1.3' or lowerAffected if The version displayed is 2.1.3 or lower
-
Verify the application handles user inputReview PHP source files for dynamic function calls, include/require statements using variables, or file operation functions (file_get_contents, unlink, etc.) that process user-supplied inputAffected if The application passes user input to PHP execution functions without sanitization
A user is affected if either La Cooda Wiz version 1.4.0 or lower, or Lacoodast version 2.1.3 or lower, is installed and the application processes user input in an unsafe manner.
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 dataGiven the critical severity and RCE capability, affected instances should be isolated or taken offline immediately. Upgrade to versions beyond 1.4.0/2.1.3 if available, or migrate to a maintained alternative. If upgrade path does not exist, implement strict web application firewall rules and restrict network access to these applications.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3737 — 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-3737 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