CVE-2007-0178
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 info.php in Easy Banner Pro 2.8 allows remote attackers to execute arbitrary PHP code via a URL in the s[phppath] 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 Easy Banner Pro 2.8's info.php allows arbitrary PHP code execution through the unsanitized s[phppath] parameter. Attackers can supply a remote URL containing malicious PHP code that gets included and executed by the PHP interpreter.
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.8CVSS 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.
-
Locate Easy Banner Pro installationSearch the web server document root for files named 'info.php' or directories containing 'easy-banner' or 'EasyBannerPro'. Check common paths like /admin/, /banner/, or /phpbb/ for the application.Affected if Easy Banner Pro version 2.8 is found installed on the server
-
Identify the version numberExamine the application's header file, version.php, or any readme/install file within the Easy Banner Pro directory to confirm the exact version installed.Affected if The installed version is exactly 2.8 (the only affected version per this CVE)
-
Verify info.php exists and is web-accessibleCheck for the presence of info.php in the Easy Banner Pro installation directory. Attempt to access it via HTTP if the application is publicly reachable.Affected if info.php exists and is accessible via the web application
-
Check PHP allow_url_include settingCreate a PHPinfo page or check the active php.ini file for the allow_url_include directive. Alternatively, run: php -i | grep allow_url_include from command line.Affected if allow_url_include is set to On (On allows remote file inclusion attacks to succeed)
-
Check PHP allow_url_fopen settingReview php.ini or run php -i | grep allow_url_fopen to verify the allow_url_fopen directive setting.Affected if allow_url_fopen is set to On (this setting also permits RFI attacks when allow_url_include is off)
The environment is affected if Easy Banner Pro version 2.8 is installed with web-accessible info.php and PHP's allow_url_include or allow_url_fopen 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 allow_url_include and allow_url_fopen in php.ini; implement strict input validation on the s[phppath] parameter using whitelist validation; upgrade to a patched version if available; consider deploying a WAF rule to block RFI attempts.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0178 — 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-0178 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