# CVE-2007-4948: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via URL parameters if .htaccess support is not configured as per installation instructions.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cvp9-hwc6-x9xf

## What is CVE-2007-4948?

CVE-2007-4948 is a medium-severity code injection vulnerability in n/a, published on 18 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2007-4948?

It affects 1 product.


Products: Webmedia Explorer Webmedia Explorer.

## How do I fix CVE-2007-4948?

No fix has been published for CVE-2007-4948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-4948 being exploited?

There is no known exploitation of CVE-2007-4948 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-5252](https://insights.sbomify.com/CVE-2006-5252/): Code injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4948 and fix it if it is affected.

What it is: CVE-2007-4948 is a medium-severity code injection vulnerability in n/a, published on 18 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4948 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-4948/ (Markdown: https://insights.sbomify.com/CVE-2007-4948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-4948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-4948
- OSV: https://osv.dev/vulnerability/CVE-2007-4948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-4948/
Summaries are generated and may contain mistakes; the official description above is the record.