CVE-2008-3769
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 · uneditedPHP remote file inclusion vulnerability in admin/create_order_new.php in Freeway 1.4.1.171, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the include_page parameter.
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 confidenceRemote file inclusion vulnerability in Freeway e-commerce software version 1.4.1.171 allows attackers to execute arbitrary PHP code through the include_page parameter in admin/create_order_new.php when PHP's register_globals setting is enabled.
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.1.171CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Freeway installationLocate the Freeway e-commerce software installation directory on your server. Common paths include /var/www/, /home/*/public_html/, or C:\inetpub\wwwroot\ on Windows. Look for directories named 'freeway', 'openfreeway', or containing 'freeway' in file names.Affected if Freeway software is present on the server
-
Determine Freeway versionCheck the version file or header within the Freeway installation. Common version indicators include a version.php file, README file, or the main index.php header comments. Compare the discovered version against 1.4.1.171.Affected if Installed version is exactly 1.4.1.171
-
Locate vulnerable scriptVerify the presence of the file admin/create_order_new.php within the Freeway installation directory. This file should exist in the 'admin' subfolder.Affected if The file admin/create_order_new.php exists in the Freeway installation
-
Check PHP register_globals settingCreate a PHP info file (info.php) containing '<?php phpinfo(); ?>' in your web root, access it via browser, and search for the 'register_globals' directive. Alternatively, check your php.ini configuration file for 'register_globals = On'.Affected if PHP register_globals is set to On or enabled
You are affected only if Freeway version 1.4.1.171 is installed, the file admin/create_order_new.php exists, AND PHP's register_globals setting is enabled.
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 dataDisable PHP's register_globals setting in php.ini or upgrade to PHP 5.4+ where it was removed, and apply any available security patches to Freeway software.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3769 — 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-3769 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