# CVE-2010-5019: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the alb parameter in view_photo.php, potentially compromising the database.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hqm3-mj3r-89fx

## What is CVE-2010-5019?

CVE-2010-5019 is a high-severity SQL injection vulnerability in n/a, published on 2 Nov 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in view_photo.php in 2daybiz Online Classified Script allows remote attackers to execute arbitrary SQL commands via the alb parameter.

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

## Which versions are affected by CVE-2010-5019?

It affects 1 product.


Products: 2daybiz Online Classified Script.

## How do I fix CVE-2010-5019?

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

## Is CVE-2010-5019 being exploited?

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

Public exploit code:

- 2DayBiz Online Classified System - SQL Injection / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5019 and fix it if it is affected.

What it is: CVE-2010-5019 is a high-severity SQL injection vulnerability in n/a, published on 2 Nov 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-5019 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-2010-5019/ (Markdown: https://insights.sbomify.com/CVE-2010-5019/index.md)
```

## Sources

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

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