CVE-2007-1288
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 Webmobo WB News 1.4.1 and earlier allow remote attackers to execute arbitrary PHP code via a URL in the config[installdir] parameter to (1) comment.php, (2) themes.php, (3) directory.php, and (4) sendmsg.php in admin/.
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 Webmobo WB News 1.4.1 and earlier allows remote attackers to execute arbitrary PHP code by supplying a malicious URL in the config[installdir] parameter to multiple admin PHP files (comment.php, themes.php, directory.php, sendmsg.php). The application includes files based on user-controlled input without proper validation, enabling RFI attacks.
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.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
- 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.
-
Locate Webmobo WB News installationSearch the web server document root for the 'wbnews' or 'wb news' directory, or look for files named 'index.php' that contain 'WB News' or 'webmobo' in the HTML title or source.Affected if The application is found on the server.
-
Determine installed versionCheck for a version file, or look in the main index.php or a config file for a version number or release date. Common paths include /wbnews/, /news/, or the root of the WB News installation.Affected if The version is 1.4.1 or any version lower than 1.4.1.
-
Verify vulnerable admin scripts existCheck if these files exist in the admin directory: comment.php, themes.php, directory.php, sendmsg.php. These are typically found in /admin/ subdirectory of the WB News installation.Affected if One or more of these admin PHP files exist and are accessible via the web server.
-
Confirm exploitable parameter handlingReview the source code of the admin PHP files to verify they include files based on $_POST or $_GET parameters, specifically checking if 'config[installdir]' is used in include/require statements without validation.Affected if The code uses the config[installdir] parameter in include/require statements without sanitization.
The environment is affected if Webmobo WB News version 1.4.1 or lower is installed and the vulnerable admin scripts (comment.php, themes.php, directory.php, sendmsg.php) are accessible, as they allow user-controlled input to dictate which files are included.
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 allow_url_fopen and allow_url_include in PHP configuration to prevent remote file inclusion. Implement strict input validation on the config[installdir] parameter to ensure only expected values are accepted, or upgrade to a patched version if available.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1288 — 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-1288 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