# CVE-2005-4260: Cross-site scripting in n/a

> Remote attackers can execute cross-site scripting attacks in PHP-Nuke by exploiting browser interpretation conflicts to bypass input sanitization.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-355w-pfx5-w3wr

## What is CVE-2005-4260?

CVE-2005-4260 is a medium-severity cross-site scripting vulnerability in Francisco Burzi Php-Nuke, published on 15 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Interpretation conflict in includes/mainfile.php in PHP-Nuke 7.9 and later allows remote attackers to perform cross-site scripting (XSS) attacks by replacing the ">" in the tag with a "<", which bypasses the regular expressions that sanitize the data, but is automatically corrected by many web browsers.  NOTE: it could be argued that this vulnerability is due to a design limitation of many web browsers; if so, then this should not be treated as a vulnerability in PHP-Nuke.

## Which versions are affected by CVE-2005-4260?

It affects 1 product.


Products: Francisco Burzi Php-Nuke.

## How do I fix CVE-2005-4260?

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

## Is CVE-2005-4260 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4260 exists.

Public exploit code:

- PHP-Nuke 7.x - Content Filtering Bypass (exploitdb)

## Other vulnerabilities in Francisco Burzi Php-Nuke

- [CVE-2005-3016](https://insights.sbomify.com/CVE-2005-3016/): Other in n/a (critical 10.0)
- [CVE-2001-1025](https://insights.sbomify.com/CVE-2001-1025/): SQL injection in n/a (critical 10.0)
- [CVE-2001-0320](https://insights.sbomify.com/CVE-2001-0320/): Path traversal in n/a (critical 10.0)
- [CVE-2007-6376](https://insights.sbomify.com/CVE-2007-6376/): Path traversal in n/a (high 7.5)
- [CVE-2003-1435](https://insights.sbomify.com/CVE-2003-1435/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4260 and fix it if it is affected.

What it is: CVE-2005-4260 is a medium-severity cross-site scripting vulnerability in Francisco Burzi Php-Nuke, published on 15 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4260 exists.

Affected product: Francisco Burzi Php-Nuke. 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-2005-4260/ (Markdown: https://insights.sbomify.com/CVE-2005-4260/index.md)
```

## Sources

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

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