dbcve.org
Webmedia ExplorerApplication

CVE-2007-4948

MEDIUM · 5.1 CVSS v2.0 Published 2007-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Webmedia Explorer (webmex) 3.2.2 allow remote attackers to execute arbitrary PHP code via (1) a URL in the path_include parameter to includes/rss.class.php, (2) a URL in the path_template parameter to (a) templates/main.tpl.php or (b) templates/folder_messages_link_message_name.tpl.php, or (4) a URL in the path_templates parameter to templates/sidebar.tpl.php. NOTE: the vulnerability is present only when the administrator does not follow installation instructions about the requirement for .htaccess support. NOTE: the includes/core.lib.php vector is already covered by CVE-2006-5252.

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 confidence

Multiple remote file inclusion vulnerabilities in Webmedia Explorer 3.2.2 allow attackers to inject arbitrary PHP code through uncontrolled path parameters (path_include, path_template, path_templates) in various template and include files. Exploitation succeeds when administrators fail to implement required .htaccess protection during installation.

MitigationEnsure .htaccess support is properly configured during installation per vendor instructions, or apply vendor patches that sanitize the vulnerable path parameters to prevent URL-based file inclusion.

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
Webmedia ExplorerApplication
Affected:= 3.2.2

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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/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. Identify Webmedia Explorer installation and version
    Locate the Webmedia Explorer installation directory and check for version information in the main file (typically index.php, version.php, or similar). Compare the installed version to 3.2.2.
    Affected if The installed version is Webmedia Explorer 3.2.2 exactly.
  2. Verify vulnerable script files exist
    Check if the template and include files containing the vulnerable path parameters (path_include, path_template, path_templates) exist in the installation. Common paths include files under /include/ or /template/ directories.
    Affected if The vulnerable include files are present and accessible in the web directory.
  3. Confirm .htaccess protection status
    Inspect the .htaccess file in the Webmedia Explorer root and subdirectories to determine if protection rules are properly configured to block direct access to the vulnerable parameters.
    Affected if No .htaccess file exists, or the existing .htaccess does not restrict access to the vulnerable path parameters.
  4. Test parameter accessibility via HTTP
    Attempt to access one of the vulnerable script files with a manipulated path_include, path_template, or path_templates parameter pointing to an external URL. If the server processes the inclusion, the vulnerability is present.
    Affected if The vulnerable parameters accept and process external URLs without sanitization.

A user is affected if Webmedia Explorer version 3.2.2 is installed AND the .htaccess protection was not properly configured during installation, allowing the path_include, path_template, or path_templates parameters to accept untrusted input.

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

Ensure .htaccess support is properly configured during installation per vendor instructions, or apply vendor patches that sanitize the vulnerable path parameters to prevent URL-based file inclusion.

Fix this in Webmedia Explorer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4948 — 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-4948 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