# CVE-2006-4748: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via multiple parameters in F-ART BLOG:CMS plugins, potentially compromising database integrity and confidentiality.

- **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:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v8qv-pq5m-hg2w

## What is CVE-2006-4748?

CVE-2006-4748 is a high-severity SQL injection vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in F-ART BLOG:CMS 4.1 allow remote attackers to execute arbitrary SQL commands via the (1) xagent, (2) xpath, (3) xreferer, and (4) xdns parameters in (a) admin/plugins/NP_Log.php, and the (5) pitem parameter in (b) admin/plugins/NP_Poll.php; and allow remote authenticated users to execute arbitrary SQL commands via the (6) pageRef parameter in (c) admin/plugins/NP_Referrer.php.

## Which versions are affected by CVE-2006-4748?

It affects 1 product.


Products: F-Art Agency Blog Cms.

## How do I fix CVE-2006-4748?

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

## Is CVE-2006-4748 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3364](https://insights.sbomify.com/CVE-2006-3364/): SQL injection in n/a (high 7.5)
- [CVE-2006-6035](https://insights.sbomify.com/CVE-2006-6035/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2005-4687](https://insights.sbomify.com/CVE-2005-4687/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4748 and fix it if it is affected.

What it is: CVE-2006-4748 is a high-severity SQL injection vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4748 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-2006-4748/ (Markdown: https://insights.sbomify.com/CVE-2006-4748/index.md)
```

## Sources

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

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