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

> Authenticated users can execute arbitrary SQL commands via the id parameter in plx Auto Reminder, potentially compromising database integrity.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w9qv-f37g-g59w

## What is CVE-2009-0593?

CVE-2009-0593 is a medium-severity SQL injection vulnerability in n/a, published on 16 Feb 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in members.php in plx Auto Reminder 3.7 allows remote authenticated users to execute arbitrary SQL commands via the id parameter in a newar action.

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

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

It affects 1 product.


Products: Plxwebdev Plx Auto Reminder.

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

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

## Is CVE-2009-0593 being exploited?

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

Public exploit code:

- plxAutoReminder 3.7 - 'id' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0593 is a medium-severity SQL injection vulnerability in n/a, published on 16 Feb 2009. Any signed-in user can exploit it 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-0593 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-0593/ (Markdown: https://insights.sbomify.com/CVE-2009-0593/index.md)
```

## Sources

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

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