MoodleCMS
CVE-2007-1429
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in Moodle 1.7.1 allow remote attackers to execute arbitrary PHP code via a URL in the cmd parameter to (1) admin/utfdbmigrate.php or (2) filter.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 confidenceMoodle 1.7.1 contains remote file inclusion vulnerabilities in admin/utfdbmigrate.php and filter.php. The cmd parameter in these scripts allows remote attackers to specify a URL to an external PHP file, which Moodle will then include and execute on the server, granting arbitrary code execution.
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
MoodleCMS
= 1.7.1CVSS 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.
-
Confirm Moodle versionLocate and inspect the version.php file in your Moodle installation root or access the admin interface to view the installed version numberAffected if The installed version is exactly 1.7.1 (Moodle 1.7.1)
-
Verify vulnerable script existenceCheck if the files admin/utfdbmigrate.php and filter.php exist in the web-accessible Moodle directoryAffected if These PHP files exist and are present in the installation
-
Test script accessibilityAttempt to access these scripts directly via HTTP to determine if they are reachable without authentication (e.g., GET request to admin/utfdbmigrate.php and filter.php)Affected if The scripts respond to HTTP requests (even with an error or empty response)
-
Check PHP remote inclusion settingsInspect PHP configuration files (php.ini) or use phpinfo() to check if allow_url_fopen or allow_url_include directives are enabledAffected if allow_url_fopen or allow_url_include is set to On (these settings enable RFI attacks)
-
Inspect cmd parameter handlingReview the source code of admin/utfdbmigrate.php and filter.php to confirm they accept and process a cmd parameter without sanitizationAffected if The scripts accept a cmd parameter that gets passed to include/require statements without validation
A user is affected if they are running exactly Moodle 1.7.1, the vulnerable scripts are accessible, PHP allows URL inclusion, and the cmd parameter is being processed unsafely in the affected files.
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 dataUpgrade Moodle to a patched version beyond 1.7.1, or apply vendor-supplied patches to these specific files. If immediate patching is not feasible, disable these scripts or deploy a WAF rule to block cmd parameter manipulation.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1429 — 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-2007-1429 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