# CVE-2005-0725: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the articleid parameter in the WF-Sections plugin, potentially compromising database integrity.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w26q-jp2w-2hvw

## What is CVE-2005-0725?

CVE-2005-0725 is a high-severity SQL injection vulnerability in n/a, published on 12 Mar 2005. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the getAllbyArticle function in wfsfiles.php for WF-Sections (wfsections) 1.07 allows remote attackers to execute arbitrary SQL commands via the articleid parameter to article.php.

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

It affects 1 product.


Products: Wf-Sections Wf-Sections.

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

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

## Is CVE-2005-0725 being exploited?

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

Public exploit code:

- XOOPS Module WF-Section 1.01 - 'articleId' SQL Injection (exploitdb)
- XOOPS Module XFsection 1.07 - 'articleId' Blind SQL Injection (exploitdb)
- XOOPS Module Zmagazine 1.0 - 'print.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1974](https://insights.sbomify.com/CVE-2007-1974/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0725 is a high-severity SQL injection vulnerability in n/a, published on 12 Mar 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0725 exists.

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

## Sources

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

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