# CVE-2005-3016: Other in n/a

> Unspecified vulnerabilities in the PHP-Nuke WYSIWYG editor allow attackers to potentially compromise the web application.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 21 Sep 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-chrc-r4w7-3466

## What is CVE-2005-3016?

CVE-2005-3016 is a critical vulnerability in Francisco Burzi Php-Nuke, published on 21 Sep 2005. It can be exploited over the network.

### Official description

Multiple unspecified vulnerabilities in the WYSIWYG editor in PHP-Nuke before 7.9 Final have unknown impact and attack vectors.

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

It affects 1 product.


Products: Francisco Burzi Php-Nuke.

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

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

## Is CVE-2005-3016 being exploited?

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

## Other vulnerabilities in Francisco Burzi Php-Nuke

- [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)
- [CVE-2007-0372](https://insights.sbomify.com/CVE-2007-0372/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3016 is a critical vulnerability in Francisco Burzi Php-Nuke, published on 21 Sep 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-3016 in the wild and no public exploit code.

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-3016/ (Markdown: https://insights.sbomify.com/CVE-2005-3016/index.md)
```

## Sources

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

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