dbcve.org
B2evolutionApplication

CVE-2007-2358

HIGH · 7.5 CVSS v2.0 Published 2007-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Multiple PHP remote file inclusion vulnerabilities in b2evolution allow remote attackers to execute arbitrary PHP code via a URL in the (1) inc_path parameter to (a) a_noskin.php, (b) a_stub.php, (c) admin.php, (d) contact.php, (e) default.php, (f) index.php, and (g) multiblogs.php in blogs/; the (2) view_path and (3) control_path parameters to blogs/admin.php; and the (4) skins_path parameter to (h) blogs/contact.php and (i) blogs/multiblogs.php. NOTE: this issue is disputed by CVE, since the inc_path, view_path, control_path, and skins_path variables are all initialized in conf/_advanced.php before they are used

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 confidence

Remote file inclusion vulnerability in b2evolution allowing arbitrary PHP code execution via URL parameters (inc_path, view_path, control_path, skins_path) in multiple PHP files within the blogs/ directory. NOTE: CVE indicates this issue is DISPUTED because the variables are initialized in conf/_advanced.php before use, which may prevent exploitation.

MitigationVerify whether path variables are properly initialized before use in all affected code paths; if uninitialized, ensure all include_path parameters are validated and hardcoded to prevent user-supplied values from being used. Consider upgrading to a supported version of b2evolution.

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
B2evolutionApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate b2evolution installation
    Search for b2evolution by checking for characteristic files such as blogs/index.php, blogs/conf/_config.php, or the presence of a 'b2evolution' directory in the web root.
    Affected if b2evolution CMS is installed on the server.
  2. Identify b2evolution version
    Check the version file or common version indicators: look for a VERSION file in the root directory, check blogs/inc/_core/_misc.php for version constants, or examine the HTML generator meta tag in any served b2evolution page.
    Affected if Any installed version of b2evolution is present (CVE states all versions are affected).
  3. Verify vulnerable files exist in blogs/ directory
    Check for the presence of affected PHP files in the blogs/ directory, including but not limited to: blogs/inc/_misc.funcs.php, blogs/inc/_template.funcs.php, or other files that reference the path parameters (inc_path, view_path, control_path, skins_path).
    Affected if The vulnerable PHP files exist and are web-accessible.
  4. Inspect variable initialization in conf/_advanced.php
    Open blogs/conf/_advanced.php and examine whether the path variables (inc_path, view_path, control_path, skins_path) are properly initialized with safe default values before any include statements that use them.
    Affected if The path variables are NOT initialized with hardcoded safe values, or initialization can be bypassed, leaving them open to user-supplied URL parameter injection.
  5. Test for parameter injection via URL
    If the above checks indicate uninitialized variables, attempt a safe test by requesting a b2evolution page with a modified path parameter (e.g., ?inc_path=http://example.com/) and observe whether the application attempts to include external content or returns an error indicating the path was used.
    Affected if The application accepts and acts upon user-supplied values for inc_path, view_path, control_path, or skins_path parameters without validation.

A user is affected if b2evolution is installed and the path variables (inc_path, view_path, control_path, skins_path) are not properly initialized with hardcoded safe values in conf/_advanced.php, allowing arbitrary URL-supplied values to be used in include/require statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Verify whether path variables are properly initialized before use in all affected code paths; if uninitialized, ensure all include_path parameters are validated and hardcoded to prevent user-supplied values from being used. Consider upgrading to a supported version of b2evolution.

Fix this in B2evolution Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2358 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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