# CVE-2009-3226: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the replid parameter in Almond Classifieds Ads Enterprise.

- **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:** 16 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5r4q-84cw-cpwc

## What is CVE-2009-3226?

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

### Official description

SQL injection vulnerability in index.php in AlmondSoft Almond Classifieds Ads Enterprise and Almond Affiliate Network Classifieds allows remote attackers to execute arbitrary SQL commands via the replid parameter in a manw_repl add_form action.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2009-3226?

It affects 2 products.


Products: Almondsoft Affiliate Network Classifieds, Almondsoft Almond Classifieds.

## How do I fix CVE-2009-3226?

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

## Is CVE-2009-3226 being exploited?

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

Public exploit code:

- AlmondSoft Multiple Classifieds Products - 'index.php?replid' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-3227](https://insights.sbomify.com/CVE-2009-3227/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3226 and fix it if it is affected.

What it is: CVE-2009-3226 is a high-severity SQL injection vulnerability in n/a, published on 16 Sep 2009. 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-2009-3226 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-2009-3226/ (Markdown: https://insights.sbomify.com/CVE-2009-3226/index.md)
```

## Sources

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

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