CVE-2007-1136
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 · uneditedindex.php in WebMplayer before 0.6.1-Alpha allows remote attackers to execute arbitrary code via shell metacharacters in an exec function call. NOTE: some sources have referred to this as eval injection in the param parameter, but CVE source inspection suggests that this is erroneous.
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 confidenceCommand injection vulnerability in WebMplayer index.php before version 0.6.1-Alpha allows remote attackers to execute arbitrary OS commands by injecting shell metacharacters into a parameter that gets passed to PHP's exec() function. This is a classic command injection flaw where user-supplied input is used unsafely in a system call.
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<= 0.6= 0.1= 0.2.1= 0.3= 0.3.1= 0.3.2= 0.3.3= 0.4= 0.5= 0.5.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
- 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.
-
Locate WebMplayer installation directorySearch the web server document root for the WebMplayer application files, specifically looking for an index.php file that belongs to WebMplayer.Affected if The WebMplayer application is present on the server
-
Determine the installed WebMplayer versionOpen the index.php file in the WebMplayer directory and search for a version string or variable (commonly defined as a constant like 'VERSION' or '$version'). Alternatively, check for a separate VERSION or CHANGELOG file in the application root.Affected if The version returned is 0.6 or earlier, or matches any of these: 0.1, 0.2.1, 0.3, 0.3.1, 0.3.2, 0.3.3, 0.4, 0.5, or 0.5.1
-
Identify the vulnerable parameter in index.phpOpen index.php and search for calls to PHP exec(), system(), shell_exec(), or passthru() functions. Examine whether any user-supplied parameters (from $_GET, $_POST, or $_REQUEST) are passed directly to these functions without sanitization.Affected if User input from request parameters is used unsafely in an exec() call without proper escaping or validation
You are affected if WebMplayer version 0.6 or earlier is installed and the index.php file contains direct use of user-supplied parameters in exec() calls.
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 to WebMplayer 0.6.1-Alpha or later. If upgrading is not feasible, implement strict input validation and sanitization on all parameters passed to exec() or other system functions to remove/reject shell metacharacters.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1136 — 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-1136 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